gemini-cli - 💡(How to fix) Fix Escape key clears prompt input instead of pausing generation [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#25477Fetched 2026-04-16 07:05:59
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

What happened?

Pressed Escape during active generation. Input field wiped completely. Previous generation stopped. Lost entire typed prompt WHICH TOOK ME A LONG TIME TO WRITE.

What did you expect to happen?

Escape pauses/stops generation only. Prompt text stays intact. Can submit new message without retyping.

Client information

  • CLI Version: 0.38.0
  • Git Commit: 3f0873a83
  • Session ID: 9173df9f-2af4-447b-b6a4-48e763a76d06
  • Operating System: linux v25.9.0
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 657.6 MB
  • Terminal Name: Konsole 25.12.3
  • Terminal Background: #232627
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

I don't think it's a bug, Bug please add in settings as feature to Toggle or something I BEG PLEASE!

extent analysis

TL;DR

The issue can be potentially resolved by adding a feature to toggle the behavior of the Escape key during active generation, allowing users to choose whether the input field should be wiped or not.

Guidance

  • The current behavior of the Escape key wiping the input field completely may be unexpected and undesirable for some users, and adding a toggle feature could provide more flexibility.
  • To verify the issue, try pressing the Escape key during active generation and observe whether the input field is wiped or not.
  • Consider adding a setting to allow users to choose the behavior of the Escape key, such as a toggle to "Pause generation without clearing input" or "Stop generation and clear input".
  • The feature request to add a toggle setting could be explored further to determine the best implementation approach.

Example

No code snippet is provided as the issue does not contain sufficient technical details to suggest a specific implementation.

Notes

The issue may not be a bug, but rather a feature request to change the current behavior of the Escape key. The solution may involve adding a new setting or toggle to provide more flexibility for users.

Recommendation

Apply workaround: Add a feature to toggle the behavior of the Escape key during active generation, allowing users to choose whether the input field should be wiped or not. This would provide more flexibility and address the user's concern.

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