Option 2 in Confirmation Menus Interpreted as Cancel/Escape on Windows
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?
Reported by: Enterprise User
Summary
When presented with interactive confirmation menus in Claude Code (e.g., edit approval prompts), selecting option 2 is consistently interpreted as option 3 (cancel/escape/No) instead of executing the intended action.
Environment
- Platform: Windows (win32)
- Claude Code Version: 2.0.32
- Node Version: v22.18.0
- Terminal: Windows Terminal / PowerShell
- User Type: Enterprise
Actual Behavior
The action is cancelled/rejected as if option 3 (No/Cancel/Escape) was selected. The plan or edit is aborted instead of being approved with session-wide permissions.
Frequency
Consistent - happens 100% of the time across all menu prompts
Impact
- Severity: High for Enterprise workflows
- Blocks ability to use "allow all for session" functionality
- Forces manual approval for every single edit/action
- Significantly degrades productivity in batch operation scenarios
- Workaround: Only option 1 works, requiring repeated confirmations
What Should Happen?
Expected Behavior
Option 2 should execute its intended action (in this example: "Yes, allow all edits during this session")
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce
- Trigger any confirmation menu in Claude Code that presents options 1/2/3 (e.g., file edit approval prompt showing):
```
Do you want to make this edit to CLAUDE.md?
❯ 1. Yes
- Yes, allow all edits during this session (shift+tab)
- No, and tell Claude what to do differently (esc)
```
- Select option 2 using either method:
- Method A: Press the "2" key directly
- Method B: Use arrow keys to navigate to option 2, then press Enter
- Observe the behavior
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.32
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
Additional Context
This issue is distinct from the known Shift+Tab keyboard shortcut issues on Windows (#3390, #3368, #9598). The problem occurs regardless of input method (direct numeric key press OR arrow key navigation + Enter).
Potentially related to broader Windows TUI keyboard handling issues documented in:
- #95 (Cannot interact with Claude Code interface on Windows)
- #7693 (Windows not accepting input / keystroke dropping)
- #6995 (Arrow Key Navigation Broken)
Enterprise User Note
As an Enterprise user, this significantly impacts team productivity and adoption of Claude Code for development workflows requiring multiple file edits or extended coding sessions.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗