Extend Gemini CLI OAuth Support Until Antigravity Reaches Feature Parity and Stability

[ryan-minato]

Antigravity is currently too immature to replace Gemini CLI. Forcing a migration by cutting OAuth support now will break professional workflows for paying users. We aren't asking for perfection, but we do require a tool that actually works before the old one is killed.

It is unacceptable that a internet search company released a tool without searchable documentation. There is no search bar on the web docs and no agent-friendly Markdown version for local use. Navigating the current docs is a manual waste of time that hinders the very "AI efficiency" the tool is supposed to provide.
The transition has been technically reckless. Repurposing old product IDs for a completely different framework has created a versioning nightmare. winget manifests forced to delete legacy versions just to handle the architectural shift. Google’s forced auto-updates have already broken my development environment, along with many others in the community.

I understand that in 2026, the coding agent race moves at breakneck speed. I don’t expect a perfect product on day one—Codex and Claude Code have their own flaws. However, I do expect a usable one. As paying users, while we may not have a SLA for every feature, we have a reasonable expectation of service availability. Do not force us onto a broken platform while killing the one that actually works. Please make Antigravity functional before you make it mandatory.

[kasajian]

@ryan-minato realistically, Antigravity cli will take many months to catch up. If you are using this for serious work. I think the only correct solution is to switch to llxprt-code and use gemini key directly. It's a temporary solution. Then you can focus on getting your work done, and let the Antigravity cli codebase stabilize.

[jiggy025]

Gemini CLI is indeed far more reliable than the AGY CLI, tried using it and it's so disgusting looking at it. As a temporary workaround to keep my workflows alive, Antigravity 2.0 for Desktop actually shares the exact same OAuth system as gemini-cli. Plus, it parses local files perfectly whatever SKILL.MD or custom specs you were using locally in the CLI will be read cleanly by the Desktop app. It's not a perfect fix for terminal purists, but it saves my local context from being completely broken by the forced update.

[Neinndall]

I understand that Google is a company, but as a individual user and developer, I also have the right to a minimum level of access to Google's free services. Gemini CLI was quite generous for free users, so why can't Antigravity CLI be the same? Since it's from the same development company?
I'm currently testing it, and it's impossible to work comfortably for at least two hours a day, from 19 of May that was annourcent the notice about Agy CLI, i test the quota as individual free user, and... well, 5 requests and... that's all. Now, from that day I have to wait a week to get my fee back again...

Another complaint is how is it possible that when my free quota runs out, I only get a one-week refresh? This is insane from any perspective. Gemini CLI offered a one-day refresh rate.

You're focusing everything on making the service a paid service; if you don't pay, you won't get better features. Personally, I don't think this is the right approach. These are my current complaints and feedback.

[aniruddhaadak80]

Hey there. Thanks for sharing this.

This is a really interesting idea and something we have been discussing internally. We love seeing how the community is pushing the boundaries of the CLI.

We will definitely keep this in mind for future iterations.