Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix 429 errors visible in debug view when vastly under subscription request limits [1 comments, 2 participants]

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…
GitHub stats
google-gemini/gemini-cli#25552•Fetched 2026-04-17 08:55:18
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
3
Author
empperiempperi
Participants
empperiempperigemini-cli[bot]gemini-cli[bot]
Timeline (top)
labeled ×3commented ×1

Error Message

I would expect the service to keep on working and when my request limits are reached I would get a reasonable notification or error message stating what has happened instead of the model processing getting completely stuck with no clear indication what is going on.

Fix Action

Fix / Workaround

429 errors visible under debug view with 159 requests done on 3-flash-preview and 23 on 3.1-pro-preview. 69.6% of the pro model requests failed at which point I forced the model to flash. It worked for a while and then also started to give 429 errors. As Google One AI Pro subscriber my request limit should be 1500, not under 200. This is a backend rate limit bug which has persisted for over a month now after the stated abuse mitigation was put into place. This is not abusive usage, it was agentic development for which Gemini CLI has been built for.

RAW_BUFFERClick to expand / collapse

What happened?

429 errors visible under debug view with 159 requests done on 3-flash-preview and 23 on 3.1-pro-preview. 69.6% of the pro model requests failed at which point I forced the model to flash. It worked for a while and then also started to give 429 errors. As Google One AI Pro subscriber my request limit should be 1500, not under 200. This is a backend rate limit bug which has persisted for over a month now after the stated abuse mitigation was put into place. This is not abusive usage, it was agentic development for which Gemini CLI has been built for.

As it stands, the CLI session is completely unusable and stuck and only way to see what's going on is by opening the debug view.

The issue is related to changes announced here https://github.com/google-gemini/gemini-cli/discussions/22970

<img width="1082" height="971" alt="Image" src="https://github.com/user-attachments/assets/2f8c56ed-a8ff-4750-97af-4c298a066e17" /> <img width="1051" height="1138" alt="Image" src="https://github.com/user-attachments/assets/22652c3c-edc1-494b-a1ab-28a8620afcf2" />

What did you expect to happen?

I would expect the service to keep on working and when my request limits are reached I would get a reasonable notification or error message stating what has happened instead of the model processing getting completely stuck with no clear indication what is going on.

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: b9075c0e-c19e-4182-bd5c-9a88e6b7be43
  • Operating System: win32 v25.2.1
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 453.9 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

Google Account via OAuth, using Google One AI Pro subscription.

Anything else we need to know?

This is a critical issue plaguing all users and practically rendering the service unusable. I like Gemini, I want to support you but as it stands you are making it very hard.

extent analysis

TL;DR

The most likely fix is to investigate and adjust the rate limiting configuration to align with the expected 1500 request limit for Google One AI Pro subscribers.

Guidance

  • Review the changes announced in the discussion https://github.com/google-gemini/gemini-cli/discussions/22970 to understand the intended rate limiting behavior.
  • Verify the current rate limiting configuration to ensure it matches the expected limits for Google One AI Pro subscribers.
  • Check for any other potential factors that could be contributing to the 429 errors, such as network issues or concurrent request limits.
  • Consider implementing a retry mechanism or exponential backoff strategy to handle rate limiting errors and prevent the service from becoming stuck.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue appears to be related to a backend rate limit bug, and the provided information suggests that the rate limiting configuration may not be correctly implemented. Further investigation is needed to determine the root cause and implement a fix.

Recommendation

Apply a workaround, such as implementing a retry mechanism or exponential backoff strategy, to mitigate the impact of the 429 errors until the underlying rate limiting issue can be resolved. This is recommended because the issue is critical and rendering the service unusable, and a workaround can provide a temporary solution while the root cause is investigated.

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…
#memory optimization#batch processing#GPU compatibility#latency issue#model 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

gemini-cli - 💡(How to fix) Fix 429 errors visible in debug view when vastly under subscription request limits [1 comments, 2 participants]