[BUG] Bug Report: Interactive UI unresponsive on Windows — raw mode not supported

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?

Claude Code launches and displays the interactive UI (trust dialog, prompts) but does not respond to any keyboard input. Pressing Enter, number keys, arrow keys, or spacebar has no effect. The UI renders correctly but is completely unresponsive. When attempting to pipe input directly (e.g. echo "1" | claude), the error below is thrown

What Should Happen?

The interactive UI should accept keyboard input and proceed past the trust dialog into the chat interface.

Error Messages/Logs

ERROR  Raw mode is not supported on the current process.stdin, which Ink uses as input stream by default.
- Read about how to prevent this error on https://github.com/vadimdemedes/ink/#israwmodesupported
- handleSetRawMode (B:/~BUN/root/src/entrypoints/cli.js:631:2077)

Steps to Reproduce

Steps to Reproduce

1. Install Claude Code on Windows (npm install -g @anthropic-ai/claude-code)
2. Open Windows Terminal, PowerShell 5, or PowerShell 7
3. Run claude in any directory
4. Observe trust dialog renders correctly
5. Press Enter or any key — no response

• UI renders but does not accept any keyboard input
• Piping input (echo "1" | claude) throws a raw mode error from Ink
• The only workaround is claude -p "prompt" with CLAUDE_DANGEROUSLY_SKIP_PERMISSIONS=true set, which bypasses the interactive UI entirely

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.69

Claude Code Version

2.1.70

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

• Issue appeared after an auto-update (was working on a prior version)
• Affects Windows Terminal, default PowerShell console (conhost), and PowerShell 7
• WSL resolves the issue but is not always available on managed/enterprise machines
• Ink's raw mode requirement appears to be incompatible with Windows console hosts in certain configurations
• Enterprise machines with group policy restrictions cannot easily install alternative terminals or WSL, making this a blocking issue for Windows enterprise users