PR #25862: fix(cli): correct backspace handling in Windows Terminal

• Repository: google-gemini/gemini-cli
• Author: secreal
• State: open | merged: False
• Link: https://github.com/google-gemini/gemini-cli/pull/25862

Description (problem / solution / changelog)

Summary

Fix incorrect backspace handling in Windows Terminal.

In some Windows Terminal setups, normal Backspace could be treated like Ctrl+Backspace, causing it to delete the previous word instead of a single character.

Details

This change narrows the Windows fallback that interprets raw \b as Ctrl+Backspace. The fallback is now disabled in Windows Terminal (WT_SESSION) and remains available only for non-Windows-Terminal Windows consoles where that behavior may still be needed.

Regression coverage was also added for the Windows Terminal case.

Related Issues

Fixes #25856

How to Validate

1. Run the targeted test:

   npm --workspace @google/gemini-cli test -- src/ui/contexts/KeypressContext.test.tsx

2. In Windows Terminal, run the CLI and type some text with a typo.
3. Press Backspace and confirm it deletes a single character.
4. Press Ctrl+Backspace and confirm it does not cause normal Backspace to be treated as word-delete.
5. Confirm the Windows Terminal regression test passes.

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

Changed files

• packages/cli/src/ui/contexts/KeypressContext.test.tsx (modified, +47/-2)
• packages/cli/src/ui/contexts/KeypressContext.tsx (modified, +9/-3)

---

PR #25882: fix(cli): restrict ctrl+backspace detection to Windows Terminal only

• Repository: google-gemini/gemini-cli
• Author: dogukanozen
• State: open | merged: False
• Link: https://github.com/google-gemini/gemini-cli/pull/25882

Description (problem / solution / changelog)

Summary

• PR #21447 introduced ctrl+backspace word deletion for Windows, but the condition OS === 'Windows_NT' was too broad
• cmd.exe and PowerShell send \b (0x08) for plain backspace, not \x7f — so they were incorrectly being treated as Ctrl+Backspace, deleting a whole word on every backspace press
• Fixed by scoping ctrl=true to WT_SESSION only (Windows Terminal), which is the only terminal that sends \b for Ctrl+Backspace and \x7f for plain backspace
• Updated the test that expected OS=Windows_NT alone to set ctrl=true

Details

Related Issues

Fixes #25867 #25856

How to Validate

Pre-Merge Checklist

<!-- Check all that apply before requesting review or merging. -->

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

Changed files

• packages/cli/src/ui/contexts/KeypressContext.test.tsx (modified, +2/-2)
• packages/cli/src/ui/contexts/KeypressContext.tsx (modified, +4/-6)