gemini-cli - 💡(How to fix) Fix Latest version is 100% failure rate with HTTP 429 using Ultra Plan [2 comments, 3 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#25526Fetched 2026-04-17 08:55:45
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
3
Timeline (top)
labeled ×3commented ×2

Code Example

> /about
# paste output here
RAW_BUFFERClick to expand / collapse

What happened?

Past 3 days have gotten substantially worse, and as of last 24 hours I have a 100% failure rate with the latest release. No exaggeration, literally 100% failure rate, every single response using the --prompt feature has failed for me or timed out. There has been ZERO response or acknowledgment of this problem from Google, you guys need to say something. This is ridiculous, and you are already the most expensive option.

What did you expect to happen?

For it to work!!!

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here
</details>

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue may be resolved by investigating the recent changes in the latest release and comparing it with the previous working version to identify the root cause of the 100% failure rate.

Guidance

  • Review the release notes and changelog of the latest release to identify any changes that could be causing the issue.
  • Run the /about command in the interactive CLI to gather client information, which may provide clues about the environment and configuration that could be contributing to the problem.
  • Test the --prompt feature with a minimal input to see if the issue is specific to certain types of prompts or if it's a general problem.
  • Consider reaching out to Google support or community forums to report the issue and seek assistance, as the 100% failure rate suggests a potentially widespread problem.

Notes

The issue lacks specific technical details, such as error messages or stack traces, which makes it difficult to provide a more targeted solution. Additionally, the lack of response from Google support may indicate a need to escalate the issue through official channels.

Recommendation

Apply workaround: Given the complete failure of the --prompt feature, it may be necessary to use alternative methods or tools to achieve the desired functionality until the issue is resolved.

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