gemini-cli - 💡(How to fix) Fix Bug on model use / usage limit reached [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#25741Fetched 2026-04-22 08:03:45
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
0
Timeline (top)
commented ×2labeled ×1
RAW_BUFFERClick to expand / collapse

What happened?

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

bug-report-history-1776769419972.json

What did you expect to happen?

I got the message "Usage limit reached for gemini-3-flash-preview." with the choice of changing model "Switch to gemini-3.1-flash-lite-preview " but I'm already on this model, and the message keep going on to display, no matter what I do.

Client information

  • CLI Version: 0.38.2
  • Git Commit: b0ed611a0
  • Session ID: 21dfc7a9-bf65-49cc-84ec-f17d338457be
  • Operating System: win32 v22.17.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3.1-flash-lite-preview
  • Auth Type: oauth-personal
  • Memory Usage: 272.7 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The user may need to wait for the usage limit to reset or contact support to resolve the "Usage limit reached" issue for the gemini-3-flash-preview model.

Guidance

  • Verify that the model version is indeed gemini-3.1-flash-lite-preview, as the error message suggests a different model.
  • Check if there are any usage limits or quotas associated with the oauth-personal auth type that may be causing the issue.
  • Consider reaching out to support for assistance with resolving the usage limit issue, as the error message does not provide a clear resolution path.
  • Review the exported chat history JSON file (if shared) to see if it contains any relevant information about the usage limit or error.

Notes

The issue may be related to the specific model or auth type being used, and without more information, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Contact support for assistance with resolving the usage limit issue, as the error message does not provide a clear resolution path.

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

gemini-cli - 💡(How to fix) Fix Bug on model use / usage limit reached [2 comments, 3 participants]