Numbered option prompts: anchor number keys to position, not just next-available index
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I have not searched existing requests (and frankly I shouldn't have to, use Claude consolidate the feedback)
Claude Code's interactive select prompts (permission prompts, AskUserQuestion-style menus, etc.) assign number keys sequentially based on how many options are present. This means the same keypress can mean different things depending on context — e.g. "2" is "Yes" in a 3-option prompt but "No" in a 2-option prompt. Since number keys select instantly on keypress (no confirmation), a habitual/muscle-memory keypress can silently trigger the wrong choice.
Proposed Solution
Suggestion: Anchor number keys to fixed semantic positions instead of sequential index — e.g. 1 = affirmative/first choice, 3 = negative/last choice, 2 = reserved for a middle/alternate option only when one exists. In a 2-option prompt, pressing "2" would then be a no-op rather than selecting the wrong option.
Arrow-key + Enter navigation already avoids this issue, but number-key selection is the faster path many users rely on, so it'd be good for it to fail safe.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_