Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Stays in thinking forever! [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#25520•Fetched 2026-04-17 08:55:51
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
2
Author
barancetin65barancetin65
Participants
barancetin65barancetin65gemini-cli[bot]gemini-cli[bot]heartk0108heartk0108
Timeline (top)
labeled ×3commented ×2
RAW_BUFFERClick to expand / collapse

What happened?

It stays in thinking forever.

bug-report-history-1776328042724.json

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

What did you expect to happen?

It should continue.

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: 80eeedc2-e192-4f85-8fa0-ad788521b59d
  • Operating System: win32 v24.14.1
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 318.8 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

OAuth

Anything else we need to know?

No response

extent analysis

TL;DR

The issue may be related to the client or model version, and attaching the exported chat history JSON file could help diagnose the problem.

Guidance

  • The client version (0.38.1) and model version (gemini-3-flash-preview) may be contributing to the issue, and checking for updates or compatibility issues could be helpful.
  • Attaching the exported chat history JSON file to the issue could provide more context and aid in diagnosing the problem.
  • Verifying the OAuth authentication and permissions may also be necessary to ensure that the issue is not related to authentication.

Notes

The provided information is limited, and without the exported chat history JSON file or more details about the issue, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Attach the exported chat history JSON file to the issue to help diagnose the problem, as it may provide valuable context and aid in identifying the root cause.

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 middleware#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING