Ctrl+Backspace (delete word) stopped working in prompt input after update to 2.1.199

Resolved 💬 1 comment Opened Jul 3, 2026 by kedleyaleph Closed Jul 3, 2026

Environment

  • OS: Windows 11
  • Terminal: WezTerm (build 20240203-110809, unchanged since Feb 2024)
  • Claude Code CLI: 2.1.199

What happened
Regression appeared right after the CLI auto-updated today (2026-07-03, ~00:50 local time). Before the update, holding Ctrl+Backspace in the prompt input deleted a full word per press. After the update:

  • Plain Backspace still works normally (deletes one character at a time)
  • Ctrl+Backspace (delete previous word) does nothing at all — no longer deletes anything

What I ruled out

  • WezTerm itself: binary unchanged since Feb 2024, no recent update
  • .wezterm.lua config: no keybinding override for Backspace/Delete/Ctrl combinations
  • OS-level: no accessibility toggle (Sticky/Filter Keys) involved, confirmed word-delete works fine in other apps (e.g. Notepad)

Given the timing (regression appeared exactly when the CLI self-updated) and that no other environment variable changed, the most likely cause is in the CLI's own terminal input parsing introduced in or around 2.1.199. No explicit changelog entry was found describing a change to word-delete/keyboard handling in that version.

Expected behavior
Ctrl+Backspace should delete the previous word in the prompt input, as it did in versions prior to today's update.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗