-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Remove Gemini CLI provider #5288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
π¦ Changeset detectedLatest commit: 654f04f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (72 files)Deleted Files (provider removal):
Modified Files:
|
I donβt fully agree that removing the Gemini CLI provider is the right conclusion here. Gemini CLI did work in previous KiloCode versions, so this looks more like a regression than an inherently broken integration. Most of the reported issues seem to be concentrated around tool / function calling, not basic text generation or the provider concept itself. Instead of removing the provider entirely, Iβd suggest: keeping Gemini CLI support at its current (basic) level; clearly documenting any limitations; focusing fixes specifically on the tool invocation / response parsing issues. βNot officially supported by Googleβ doesnβt necessarily mean it cannot be supported at all β many CLI-based integrations live in that gray area. Even minimal, best-effort support would be better than a hard removal, especially for users who already rely on it. |
|
What happens when people have this provider selected and update? Can you make sure to test that they won't go into some kind of locked up state? |
@ltastr - we understand that this will impact some users, and hope that most will be able to move over to one of the other methods (Google AI Studio BYOK or Gemini provider) that uses a Google-supported integration mechanism. |
|
I have validated that if you have a provider other than Gemini CLI (in my case anthropic) it will be preserved when you start the extension host. When I had gemini cli set as my settings, then launched the extension host, it reverted to kilo gateway. So I think we are OK, this seems like a good fallback. |
| "qwen-code", | ||
| "minimax", | ||
| ] | ||
| const excludedProviders = ["moonshot", "chutes", "cerebras", "litellm", "zai", "qwen-code", "minimax"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note - it seems like with the shorter line length prettier enforces this style.
which both are not included in AI pro plan? need paid API key right? |
@tazztone - unfortunately there is not a Google supported way to integrate today with the AI plans. If one becomes available, we would add support. We do have official support for ChatGPT subscriptions, support BYOK for Z.AI plans among others, and now also allow anonymous access to free models. |
|
well i use v4.145 and it works (for my purposes of creating commit messages and ask questions). so it seems there is no need for google to "support" it for it to work. |


This PR removes the Gemini CLI provider. It does not work well, and is not a Google supported use of Gemini CLI as well.