gemini-cli - 💡(How to fix) Fix Account-specific 429 RESOURCE_EXHAUSTED despite active Google One AI Pro plan [1 comments, 2 participants]

What happened?

Gemini CLI and Gemini Code Assist repeatedly return server-side 429 RESOURCE_EXHAUSTED errors on my Google One AI Pro account.

Gemini CLI signs in successfully and detects my plan:

Plan: Gemini Code Assist in Google One AI Pro

However, generation requests fail with:

429 Too Many Requests
RESOURCE_EXHAUSTED
reason: rateLimitExceeded

Affected endpoint:

https://cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse

I also observed quota retrieval failures from:

https://cloudcode-pa.googleapis.com/v1internal:retrieveUserQuota

What did you expect to happen?

Gemini CLI / Gemini Code Assist should generate a response normally after successful authentication, or provide a clear explanation if the account is ineligible, region-restricted, or quota-limited.

Client information

OS: Windows
Gemini CLI version: 0.40.1
Node.js: 24.14.0
Authentication method: Google account / Code Assist
Plan shown by CLI: Gemini Code Assist in Google One AI Pro
Google Cloud Project ID: gemini-code-495105

Login information

I am logging in with a Google account using the Gemini Code Assist / Google One AI Pro authentication flow, not an API key.

The CLI signs in successfully and shows:

Plan: Gemini Code Assist in Google One AI Pro

Anything else we need to know?

429.txt

This appears account-specific.

A different Google account works normally on the same Windows machine, same VS Code installation, same Gemini Code Assist extension, same Gemini CLI version, and same network.

Troubleshooting already done:

• Re-authenticated the Google account.
• Tested sign-in through a clean/private browser session.
• Cleared stale Windows, npm, VS Code, WinHTTP, and environment proxy settings.
• Confirmed WinHTTP is set to direct access.
• Tested another Google account on the same machine and network; the other account works.
• Created and configured a fresh Google Cloud project.
• Confirmed that requests reach Google and receive server-side 429 responses.

Trace IDs from x-cloudaicompanion-trace-id response headers:

ecdbd64f54ee07e8
e91ddb8428dc4eaf
1c8aae6c5b80bba4
5bdb4f0fb655bfde
e5fb6be339b9830a