[BUG] iTerm2 Cmd+Delete prints literal '0x15' instead of killing line (regression in 2.1.83)

Resolved 💬 3 comments Opened Mar 25, 2026 by gulliversgames Closed Mar 29, 2026

Description

Cmd+Delete mapped to iTerm2's "Send Hex Code" action with 0x15 (Ctrl+U / kill line) now prints the literal text 0x15 in the Claude Code input instead of clearing the line. This worked correctly in 2.1.81.

Typing Ctrl+U directly on the keyboard works fine — only the iTerm2 "Send Hex Code" action is broken.

Environment

  • Claude Code version: 2.1.83
  • Terminal: iTerm2 (macOS)
  • OS: macOS (Darwin 25.3.0)
  • Last working version: 2.1.81

iTerm2 Key Mapping

Profile → Keys → Cmd+Delete:

  • Action: Send Hex Code
  • Value: 0x15

This is a standard iTerm2 keybinding for mapping Cmd+Delete to "delete entire line" via Ctrl+U.

Steps to Reproduce

  1. In iTerm2 preferences, map Cmd+Delete to "Send Hex Code" 0x15
  2. Open Claude Code 2.1.83
  3. Type some text in the input
  4. Press Cmd+Delete

Expected Behavior

The entire line is cleared (same as pressing Ctrl+U).

Actual Behavior

The literal text 0x15 is inserted into the input.

Likely Cause

2.1.83 changelog includes readline-related changes:

  • "Added Ctrl+X Ctrl+E as an alias for opening the external editor (readline-native binding)"
  • "Fixed Ctrl+B interfering with readline backward-char at an idle prompt"

The readline input layer may have changed how hex codes sent by terminal emulators are interpreted vs. keyboard-generated control characters.

🤖 Generated with Claude Code

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗