Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Gemini cli backspace problem [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#25956•Fetched 2026-04-25 06:21:56
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
HakanadakliHakanadakli
Participants
GuardiaansGuardiaansHakanadakliHakanadakli
Timeline (top)
commented ×1labeled ×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?

GEMINI CLI - WINDOWS KEYBOARD BUG REPORT

Date: 04/25/2026 05:12:26 OS: Win32 (Windows 10/11) Issue: Backspace and Ctrl+Backspace are inverted. Debug Data:

  • Backspace Key: { name: "backspace", sequence: "" }
  • Ctrl+Backspace Key: { name: "backspace", ctrl: true, sequence: "\b" } Attempted Fixes:
  1. keybindings.json (sequence and key name based) - FAILED
  2. ui.terminalBuffer (true/false) - FAILED
  3. Unbinding default commands - FAILED
  4. Raw signal mapping (ctrl+h, \b) - FAILED Conclusion: Core input engine bug in Windows terminal signal handling.

Client information

  • CLI Version: 0.39.1
  • Git Commit: 4d73f3413
  • Session ID: 608db0c1-6b1d-4348-a7a8-2552b779e9b9
  • Operating System: win32 v20.19.3
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 280.2 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

The issue is likely due to a core input engine bug in Windows terminal signal handling, and a workaround may involve manually mapping keyboard signals.

Guidance

  • Verify the issue by checking the keyboard signal handling in the Windows terminal settings.
  • Attempt to manually map the Backspace and Ctrl+Backspace keys to their correct sequences.
  • Check if there are any existing issues or pull requests related to keyboard signal handling in the Gemini CLI repository.
  • Consider testing the Gemini CLI on a different operating system or terminal to isolate the issue.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue seems to be specific to the Windows operating system and the Gemini CLI. The attempted fixes listed in the issue report did not resolve the problem, suggesting a deeper issue with the input engine.

Recommendation

Apply workaround: The issue is likely a bug in the core input engine, and a workaround may be necessary until a fix is available. Manually mapping keyboard signals or using a different terminal may resolve 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…
#prompt template#agent execution#callback error#memory management#API rate limit

Still need to ship something?

×6

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

Back to top recommendations

TRENDING