Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix [Feature Request / Regression] Bring back standalone Gemini CLI or support full legacy workflow with stable OAuth

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The recent forced unification of the Gemini CLI into the Antigravity ecosystem has caused a severe regression in developer experience and productivity. While the multi-agent vision of Antigravity is understandable, deprecating the stable, lightweight Gemini CLI approach or heavily restricting its OAuth workflow has broken existing autonomous agentic (AGY) setups.

Currently, attempting to develop via the legacy workflow or utilizing the OAuth authentication method leads to extremely unstable rate-limiting. Users are facing 429 Resource Exhausted or temporary session lockouts after just 2 or 3 multi-turn prompts. The token management and local project context handling feel completely disrupted compared to the previous seamless terminal experience.

Suggested Solutions We urge the maintainers to consider the following options to prevent abandoning the existing developer base:

Maintain a Standalone Legacy Track: Keep the lightweight Gemini CLI alive as a separate, officially supported package for developers who prefer single-agent terminal environments without the overhead of a full multi-agent IDE wrapper.

Fix and Stabilize OAuth Quota in AGY Workflows: If integration is mandatory, optimize how OAuth-based authentication handles rapid sub-requests triggered by AGY loops. The current sub-second request bursts from terminal agents shouldn't completely lock out an OAuth session within 2 turns.

Provide Clear Compatibility Flags: Allow users to run the CLI in a native, decoupled mode that mimics the exact behavior, context-loading mechanics, and terminal interface of the original Gemini CLI.

Root Cause

The recent forced unification of the Gemini CLI into the Antigravity ecosystem has caused a severe regression in developer experience and productivity. While the multi-agent vision of Antigravity is understandable, deprecating the stable, lightweight Gemini CLI approach or heavily restricting its OAuth workflow has broken existing autonomous agentic (AGY) setups.

Currently, attempting to develop via the legacy workflow or utilizing the OAuth authentication method leads to extremely unstable rate-limiting. Users are facing 429 Resource Exhausted or temporary session lockouts after just 2 or 3 multi-turn prompts. The token management and local project context handling feel completely disrupted compared to the previous seamless terminal experience.

Suggested Solutions We urge the maintainers to consider the following options to prevent abandoning the existing developer base:

Maintain a Standalone Legacy Track: Keep the lightweight Gemini CLI alive as a separate, officially supported package for developers who prefer single-agent terminal environments without the overhead of a full multi-agent IDE wrapper.

Fix and Stabilize OAuth Quota in AGY Workflows: If integration is mandatory, optimize how OAuth-based authentication handles rapid sub-requests triggered by AGY loops. The current sub-second request bursts from terminal agents shouldn't completely lock out an OAuth session within 2 turns.

Provide Clear Compatibility Flags: Allow users to run the CLI in a native, decoupled mode that mimics the exact behavior, context-loading mechanics, and terminal interface of the original Gemini CLI.

RAW_BUFFERClick to expand / collapse

Description The recent forced unification of the Gemini CLI into the Antigravity ecosystem has caused a severe regression in developer experience and productivity. While the multi-agent vision of Antigravity is understandable, deprecating the stable, lightweight Gemini CLI approach or heavily restricting its OAuth workflow has broken existing autonomous agentic (AGY) setups.

Currently, attempting to develop via the legacy workflow or utilizing the OAuth authentication method leads to extremely unstable rate-limiting. Users are facing 429 Resource Exhausted or temporary session lockouts after just 2 or 3 multi-turn prompts. The token management and local project context handling feel completely disrupted compared to the previous seamless terminal experience.

Suggested Solutions We urge the maintainers to consider the following options to prevent abandoning the existing developer base:

Maintain a Standalone Legacy Track: Keep the lightweight Gemini CLI alive as a separate, officially supported package for developers who prefer single-agent terminal environments without the overhead of a full multi-agent IDE wrapper.

Fix and Stabilize OAuth Quota in AGY Workflows: If integration is mandatory, optimize how OAuth-based authentication handles rapid sub-requests triggered by AGY loops. The current sub-second request bursts from terminal agents shouldn't completely lock out an OAuth session within 2 turns.

Provide Clear Compatibility Flags: Allow users to run the CLI in a native, decoupled mode that mimics the exact behavior, context-loading mechanics, and terminal interface of the original Gemini CLI.

Why is this needed?

Many developers integrated the Gemini CLI into their daily terminal workflows and custom automation tools. Forcing a sudden architectural migration to Antigravity—while simultaneously making the alternative OAuth experience practically unusable—is severely crippling dev velocity.

Please bring back the reliable Gemini CLI workflow or provide a fully stabilized backward-compatibility layer.

Additional context

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING