A concrete data point from 0.153.4 on the terminal side of this, now that the Vim-only undo has landed.

Terminal users who remap Cmd+Z have nothing to bind it to. A common macOS setup remaps Cmd+Z at the terminal level to 0x1f (Ctrl+_), the readline undo byte — in Ghostty that is:

keybind = super+z=text:\x1f

Claude Code's composer treats 0x1f as undo. Codex drops it silently — verified by sending the raw byte into a live 0.153.4 composer: draft unchanged, no feedback.

And there is no action to remap it onto. /keymap in 0.153.4 lists 138 configurable actions; searching undo returns exactly two, both in vim_normal — Undo (u) and Redo (ctrl-r). The tui.keymap.editor.* namespace has no undo/redo entry at all. ctrl-z is not a fallback either: the keymap validator rejects it outright ("ctrl-z is reserved for suspending the terminal on Unix").

Vim mode is not a usable workaround for non-modal users. Repro on 0.153.4 with -c tui.vim_mode_default=true:

Esc Esc opens the transcript/backtrack overlay; q leaves it — the composer is left in Normal mode with no prompt to say so beyond the status hint.
Type hello there — h/e/l/l move the cursor, o opens a line and drops into Insert, and only there survives as text.

Two smaller costs in the same mode: backtrack needs three Esc presses instead of two (the first is consumed switching modes), and undo granularity is the whole insert session, so u wipes an entire draft rather than the last edit.

Ask: add editor.undo / editor.redo actions to the editor keymap context so non-modal users can bind them. A default in the readline family (ctrl-_ / ctrl-/) would match the emacs-style bindings the composer already implements, sidestep the reserved ctrl-z, and give terminal-level Cmd+Z remaps something real to land on.

Undo / redo typing #2379

Description

What feature would you like to see?

Are you interested in implementing this feature?

Additional information

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions