gemini-cli - 💡(How to fix) Fix All versions after 0.34.0 are unusable and hang for hours on resume or mid execution. [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#25504Fetched 2026-04-16 07:05:27
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
2
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

Code Example

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

What happened?

Considering cloning this repo and modifying gemini-cli to expose real logging to reveal what this and what's going on

What did you expect to happen?

Fix this. It's happening to absolutely everyone from what I can see and the tool is totally unusable at the moment. This is the number 1 priority issue. Drop everything else and deal with this.

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?

It's been happening for me since 0.35.0 so the 25th March. Could be something to do with this: JIT Context Discovery: Implemented Just-In-Time context discovery for file system tools to improve model performance and accuracy

extent analysis

TL;DR

The issue with the gemini-cli tool may be related to the Just-In-Time context discovery feature introduced in version 0.35.0, and modifying the tool to expose real logging could help reveal the cause.

Guidance

  • Review the release notes for version 0.35.0 to understand the changes made for Just-In-Time context discovery and how it might be impacting the tool's performance.
  • Clone the repository and modify the gemini-cli to enable detailed logging, as suggested, to gather more information about the issue.
  • Run the /about command in the interactive CLI to gather client information, which might be useful in troubleshooting the issue.
  • Consider reverting to a previous version of the tool, if possible, to see if the issue persists, which could help confirm if the problem is indeed related to the changes made in version 0.35.0.

Notes

The provided information does not include specific error messages or detailed descriptions of the issue, making it challenging to provide a precise fix. The suggestions are based on the information given and the potential impact of the Just-In-Time context discovery feature.

Recommendation

Apply workaround: Modify the gemini-cli to expose real logging to gather more information about the issue, as this could provide valuable insights into what's causing the problem and guide further troubleshooting or fixes.

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