[BUG] Permission prompt number key selection broken — types instead of selecting

Resolved 💬 4 comments Opened Feb 23, 2026 by Gautatyr Closed Mar 26, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

When Claude Code shows a permission prompt (e.g., "Do you want to proceed?"), pressing a number key (like 2) to select an option no longer works. Instead of selecting "Yes, and don't ask again for X", pressing 2 types the character 2 into the input line. The prompt then resolves as a single-shot permission (option 1 behavior).

The cursor can still be moved with arrow keys, and Enter still confirms the highlighted option. Only the number-key shortcut is broken.

Example of what happens when pressing 2:

 Do you want to proceed?
   1. Yes
 ❯ 2. Yes, and don't ask again for: bat:*
   3. No

The 2 gets typed into the input line instead of selecting option 2.

What Should Happen?

Pressing 2 should immediately select option 2, as it did in v2.1.41 and earlier.

Steps to Reproduce

  1. Start a Claude Code session (any terminal)
  2. Give a prompt that triggers a tool requiring permission (e.g., a Bash command not in the allow list)
  3. When the permission prompt appears, press 2 on the keyboard
  4. Observe: the character 2 is typed into the input instead of selecting the second option

Is this a regression?

Yes, this worked in a previous version.

Last Working Version

2.1.41 — confirmed working. Broken on 2.1.50.

Claude Code Version

2.1.50

Platform

Anthropic API

Operating System

Linux (CachyOS/Arch) and Windows — cross-platform issue

Terminal/Shell

Multiple (foot, Windows Terminal, xterm.js via Tauri app) — not terminal-specific

Additional Information

Tested by downgrading to 2.1.41 via pacman cache on Linux — the number key selection works correctly on that version. Also confirmed broken on Windows. The regression is somewhere in the 2.1.42–2.1.50 range.

View original on GitHub ↗

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