[BUG] Ctrl+H deletes word instead of single character in Windows Terminal + clink
Status Fixed / completed
Reported on v2.1.119
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 4 comments · opened Apr 24, 2026 · closed May 21, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
In the Claude Code CLI chat input, pressing Ctrl+H deletes an entire word backward
instead of a single character. This is the behavior of Ctrl+Backspace/backward-kill-word,
not the expected backward-delete-char (single character deletion).
This is a regression — it worked correctly in a previous version.
My environment is:
- OS: Windows 10 Pro 22H2, Windows 11
- Terminal: Windows Terminal with cmd / powershell / pwsh
- Claude Code: 2.1.119
What Should Happen?
Ctrl+H should delete single character only.
Error Messages/Logs
Steps to Reproduce
- Execute Windows Terminal
- start powershell (or pwsh or cmd)
- execute claude.exe
- input "foo bar baz", then hit CTRL+H
- "baz" is deleted, not only "z"
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.109
Claude Code Version
2.1.119
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
4 Comments
I have confirmed that this issue does not occur in WindowsTerminal 1.25 preview.
WT 1.25.11322.0 => OK
WT 1.24.11321.0 => NG
Therefore, this issue is not a CC problem but rather a WindowsTerminal issue, and the workaround appears to be to use WT 1.25preview (or later).
F.Y.I.
In WT1.25, the display created by CC seems to be prone to glitches. In particular, when returning to the previous screen after selecting options for questions, remnants of text sometimes remain. This type of corruption is something I've never seen in 1.24. It's hard to say whether this is better than being bothered by CTRL-H...
F.Y.I.
The display glitch seems to be due to a change in behavior introduced in version 1.125, which now handles East Agian ambiguous characters as wide. This likely occurs in Japanese font environments. Changing the setting back to narrow restores the previous behavior.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.