[Regression] All Cmd+* shortcuts dead in CLI prompt editor since v2.1.136 (macOS, multiple terminals)

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?

Since v2.1.136, every Cmd+* shortcut in the CLI prompt editor is swallowed on macOS — the keystroke produces no effect at all. The prompt editor behaves as if the Cmd modifier doesn't exist.

Affected combos include (non-exhaustive):

| Shortcut | Expected (macOS standard) | Actual on v2.1.136+ |
|---|---|---|
| Cmd+Left | Cursor → start of line | No effect |
| Cmd+Right | Cursor → end of line | No effect |
| Cmd+Delete | Delete from cursor to end of line | No effect |
| Cmd+Backspace | Delete from cursor to start of line | No effect |

The same combos work correctly outside Claude Code in every tested terminal (the shell prompt, vim, cat, etc.), so this is not a terminal-level interception — Claude Code is consuming or mis-routing the input itself.

Reproduces in:

• Terminal.app (native macOS, default settings)
• Warp v0.2026.05.06.15.42 (both default block UI and fullscreen mode)

This rules out a Kitty-protocol-specific cause and points squarely at Claude Code's input handler.

Empirically verified bisect (installed each version via claude install <ver> and tested in a fresh shell):

| Version | Cmd+* works? | Notes |
|---|---|---|
| 2.1.133 | ✅ Yes | Last known good |
| 2.1.134 | — | Never released (installer 404, no GitHub release) |
| 2.1.135 | — | Never released (installer 404, no GitHub release) |
| 2.1.136 | ❌ No | First broken version |
| 2.1.137 | (not retested, likely affected) | VS Code Windows activation only per changelog — inherits 2.1.136 input handler |
| 2.1.138 | ❌ No | Currently broken |

The v2.1.136 changelog includes several input-layer changes ("Fixed Backspace and Ctrl+Backspace getting swapped after Ctrl+G", "Fixed cursor landing mid-grapheme on Ctrl+E/A/K/U/arrow keys", vim operator fixes, paste-with-escape-sequence handling). One of these refactors appears to have inadvertently dropped Cmd-modifier key routing on macOS.

What Should Happen?

Standard macOS line-editing behaviour:

• Cmd+Left → cursor jumps to the start of the current line
• Cmd+Right → cursor jumps to the end of the current line
• Cmd+Backspace → delete from cursor to start of line
• Cmd+Delete → delete from cursor to end of line

This is the behaviour that existed in v2.1.133 and earlier. It is also the behaviour that issue #50503 was filed against (and previously closed/fixed) for the fullscreen TUI surface.

Error Messages/Logs

(no errors — keystroke is silently swallowed)

Steps to Reproduce

1. Install Claude Code v2.1.138 (or any version ≥ 2.1.136) on macOS:

``bash
claude install 2.1.138 --force
``

1. Open a fresh terminal (Terminal.app or Warp) and run claude.
2. In the prompt input, type:

``
hello world test
``

1. Place the cursor anywhere mid-line (e.g. with arrow keys).
2. Press Cmd+Left → expect cursor at column 0; observe: cursor does not move.
3. Press Cmd+Right → expect cursor at end; observe: cursor does not move.
4. Press Cmd+Delete → expect line cleared from cursor onward; observe: nothing happens.
5. Press Cmd+Backspace → expect text before cursor deleted; observe: nothing happens.

Recovery for affected users: downgrade to 2.1.133 (the last version with working Cmd shortcuts) and disable auto-update:

claude install 2.1.133 --force

Then set DISABLE_AUTOUPDATER=1 in settings.json env, or as an environment variable.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.133

Claude Code Version

2.1.138 (Claude Code)

Platform

Anthropic API

Operating System

macOS 26.4.1 (Darwin 25.4.0, arm64)

Terminal/Shell

Multiple — reproduces in both:

• Terminal.app (native macOS)
• Warp v0.2026.05.06.15.42 (default block UI and fullscreen mode)

Shell: zsh 5.9
TERM: xterm-256color

Additional Information

Related regressions (likely shared root cause in v2.1.136 input handler):

• #57741 — [BUG] Option+key special characters (¡ ¿ é ñ) broken in input since recent update — same surface (CLI prompt editor), different modifier (Option vs Cmd), same affected version (2.1.138)
• #57713 — Cmd+click no longer opens multiple parallel sessions after v2.1.136 update (macOS) — different surface (Desktop app), explicitly fingers v2.1.136

Historical context:

• #50503 — [Bug] Fullscreen TUI mode: Cmd+Left/Right shortcuts don't jump cursor to line start/end — closed/fixed previously; appears to have re-regressed
• #47096 — [Bug] Keyboard shortcuts broken: CMD+Backspace, CMD+Left/Right, and CMD+V for images — earlier instance (April 2026, v2.1.101), closed as duplicate

The cluster of regressions across three surfaces (CLI prompt Cmd-keys, CLI prompt Option-keys, Desktop Cmd-click) all landing in v2.1.136 strongly suggests a single underlying change to modifier-key event routing.