gemini-cli - 💡(How to fix) Fix issues where users cannot resume [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#25976Fetched 2026-04-26 05:24:21
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×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.

What did you expect to happen?

Since there have been frequent issues where users cannot resume their work using the ID displayed upon exit, it is necessary to instruct users to save their work properly before exiting. However, I believe that the token usage limit preventing this instruction from being given constitutes a very serious flaw that causes undue hardship for users.

Client information

  • CLI Version: 0.39.1
  • Git Commit: 4d73f3413
  • Session ID: 4b51dbac-f4b8-443b-940b-849a4aa87bcc
  • Operating System: linux v22.17.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 1.94 GB
  • Terminal Name: Unknown
  • Terminal Background: #282c34
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue may be resolved by re-examining the token usage limit to prevent undue hardship for users when saving their work.

Guidance

  • Review the current token usage limit and consider increasing it to accommodate user needs.
  • Investigate alternative solutions for instructing users to save their work properly before exiting, such as displaying a warning message or providing a temporary token extension.
  • Verify that the issue is indeed caused by the token usage limit by analyzing the exported chat history JSON file (if shared).
  • Consider implementing a more robust saving mechanism to reduce reliance on the token usage limit.

Notes

The provided information lacks specific details about the token usage limit and its implementation, making it challenging to provide a definitive solution.

Recommendation

Apply workaround: Implement a temporary solution to instruct users to save their work properly before exiting, such as displaying a warning message, until a more permanent fix can be developed.

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 issues where users cannot resume [1 participants]