Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix too much stall time [1 comments, 1 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#26255•Fetched 2026-05-01 05:53:04
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
1
Author
manslogicmanslogic
Participants
manslogicmanslogic
Timeline (top)
commented ×1labeled ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

What happened?

Low‑usage scenario (initial chat session): Even with very low usage, the issue begins after just 10 minutes. thinking... never end for around 14min to 30 minutes High‑usage / intensive session: Stall time reaches 14+ hours. However, this includes a large amount of work offloaded to Gemini that was not time‑sensitive and ran in the background.

[ACTION REQUIRED] report stall time or google api retry count and retry status without hiding behind thinking. make it transperant

bug-report-history-1777542154015.json

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

What did you expect to happen?

a usable session , when usage is less and not very intensive,

Client information

  • CLI Version: 0.40.0
  • Git Commit: 3d5bdc052
  • Session ID: aba8fe49-4659-4550-a3eb-cb3200ed91a6
  • Operating System: win32 v22.22.1
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 240.4 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

Report stall time and Google API retry count transparently to diagnose and potentially resolve the issue.

Guidance

  • Investigate the bug-report-history-1777542154015.json file for clues on the stall time and retry status.
  • Consider implementing a mechanism to report stall time and Google API retry count without hiding behind "thinking" to gain more insight into the issue.
  • Review the usage patterns and session intensity to understand how they impact the stall time.
  • Check the CLI version (0.40.0) and Git commit (3d5bdc052) for any known issues related to stall time or retry counts.

Notes

The issue seems to be related to the usage scenario and session intensity, but more information is needed to provide a definitive solution. The provided JSON file may hold valuable information to help diagnose the issue.

Recommendation

Apply workaround: Report stall time and Google API retry count transparently to gather more information and potentially identify the root cause of the issue.

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…
#api#authentication issue#prompt issue#agent setup#task chaining

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 too much stall time [1 comments, 1 participants]