gemini-cli - 💡(How to fix) Fix Gemini CLI Pro stuck at 0 usage [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#25238Fetched 2026-04-13 05:45:34
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

What happened?

Running anything for example "Say OK" result in infinite loop of thinking. I've notice the reset clock never reset the usage after last update.

What did you expect to happen?

Respond to command

Client information

  • CLI Version: 0.36.0
  • Git Commit: 8b1e649c2
  • Session ID: b6ea3b74-f5d4-418c-8430-755c6eca8d0b
  • Operating System: linux v22.22.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-pro-preview
  • Auth Type: oauth-personal
  • Memory Usage: 904.1 MB
  • Terminal Name: tmux 3.5a
  • Terminal Background: #000000
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue might be resolved by checking the reset clock functionality to ensure it properly resets usage after updates.

Guidance

  • Investigate the reset clock mechanism to see if it's correctly implemented and triggered after updates.
  • Verify if the infinite loop is caused by the reset clock not resetting usage, leading to continuous "thinking" loops.
  • Check the update history to see if the issue started after a specific update, potentially indicating a regression.
  • Review the memory usage (currently 904.1 MB) to ensure it's not contributing to the infinite loop.

Notes

The exact cause of the issue is unclear, and more information about the reset clock and update process would be helpful for a definitive solution.

Recommendation

Apply workaround: Implement a temporary fix to manually reset the usage after updates until the root cause of the reset clock issue is identified and 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