Terminal input regressions: permission prompt requires Enter, backspace repeat broken
Resolved 💬 2 comments Opened Feb 25, 2026 by augmentedsystems Closed Feb 25, 2026
Description
Two terminal input handling regressions in recent versions (v2.1.56). Both appeared around the same time and may share a root cause.
Bug 1: Permission prompt auto-accept broken
When Claude Code shows a permission prompt (e.g., "1) Allow once 2) Always allow"), selecting option 2 no longer auto-accepts immediately.
- Enter key now required: Previously, pressing
2would instantly accept and continue. Now it sometimes requires pressing Enter after typing2before it registers. This is inconsistent — sometimes it auto-accepts, sometimes it doesn't. - Visual glitch: After pressing
2, a snippet of the last few lines of text output appears briefly after the selection number, which looks like a rendering artifact.
Bug 2: Backspace key repeat broken
Holding down the Backspace key no longer continuously deletes characters in the Claude Code input prompt. Each character deletion requires a separate keypress. Previously, holding Backspace would repeat and delete multiple characters as expected (standard terminal key repeat behavior).
This makes editing longer prompts very tedious. Key repeat works normally in the same terminal outside of Claude Code.
Expected behavior
- Pressing
2(or1) on permission prompts should immediately accept without requiring Enter - No text artifact should appear after the selection
- Holding Backspace should continuously delete characters at the system's key repeat rate
Environment
- Claude Code CLI v2.1.56
- Linux Ubuntu (kernel 6.8.0-100-generic)
- Terminal: GNOME Terminal
- Shell: bash
Notes
- Both issues are regressions — they worked correctly in earlier versions
- Both relate to terminal input handling, possibly the same underlying change
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗