Persistent 429 Error in Gemini CLI (AI Pro Subscriber, Zero Recent Usage, Antigravity Works Fine)

Gemini API
, ,
1

Hi team,

I am experiencing the widespread 429 “Too Many Requests” (or endless “Thinking…”) error exclusively in the Gemini CLI, and I’d like to provide my data points to help isolate this bug.

Here is my current situation:

  • Account Status: I am an active Google AI Pro subscriber.

  • Zero Recent Usage: I have not used the Gemini CLI at all in the past two weeks. It is completely impossible for my account to have genuinely exhausted its quota, token limits, or triggered any real anti-abuse thresholds.

  • Isolated to CLI: This issue is strictly isolated to the Gemini CLI. My Antigravity IDE is functioning perfectly without a single rate-limit interruption.

As a front-end developer, having the terminal workflow completely blocked by a phantom 429 error—while other tools on the same Pro account work flawlessly—is highly disruptive. It strongly points to an entitlement desync specific to the CLI’s OAuth gateway.

Could the team provide an ETA on when the backend routing for Pro CLI users will be resolved?

Thank you!