Skip to content

fix: gemini api keys through openai-compatible endpoint#1834

Open
davidwarshawsky wants to merge 1 commit intosipeed:mainfrom
davidwarshawsky:fix/gemini-api-keys-mcp
Open

fix: gemini api keys through openai-compatible endpoint#1834
davidwarshawsky wants to merge 1 commit intosipeed:mainfrom
davidwarshawsky:fix/gemini-api-keys-mcp

Conversation

@davidwarshawsky
Copy link

This PR fixes an issue where Gemini API keys were failing when using the OpenAI-compatible endpoint.

Changes:

  1. Updated getDefaultAPIBase for gemini and google protocols to include the /openai suffix, which is required by Google AI Studio for OpenAI compatibility.
  2. Added google as a supported protocol in CreateProviderFromConfig.
  3. Added gemini and google to the normalizeModel list in the OpenAI-compatible provider to ensure protocol prefixes are stripped before sending the model name to Google.

These changes ensure that picoclaw can correctly route and format requests for Gemini models using its OpenAI-compatible bridge.

@sipeed-bot sipeed-bot bot added type: bug Something isn't working domain: provider go Pull requests that update go code labels Mar 20, 2026
@CLAassistant
Copy link

CLAassistant commented Mar 20, 2026

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain: provider go Pull requests that update go code type: bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants