[Bug] Claude Code TUI completely freezes on Windows startup without input

Bug Description
[BUG] [BLOCKER] Claude Code completely freezes on Windows - TUI unresponsive, no input possible, no workaround

Preflight Checklist

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

Environment

• Platform: Windows 11 (Build 10.0.26200.7705)
• Claude Code version: 2.1.31 (native install)
• Install path: C:\Users\<username>\.local\bin\claude.exe
• Install method: Native
• Terminal tested: PowerShell, CMD, Windows Terminal
• Subscription: Claude Max

Bug Description

Claude Code launches successfully and the TUI renders completely (logo, version, project path, and prompt suggestions are all visible). Hooks may even execute normally. However, after the UI appears, keyboard input is completely dead. No characters appear when typing, the cursor is stuck, and standard interrupt signals (Ctrl+C, Ctrl+Z, Esc) do not work. The only way to exit is force-closing the terminal window.

This is not a startup crash — the application loads fine. The freeze occurs in the input handling layer after the TUI is fully rendered and ready for input.

Critical Finding

The freeze is inconsistent and unpredictable:
# FREEZES - launches, renders UI, but input is dead
claude
claude --project myproject
claude --project myproject "prompt here" # Also freezes

# SOMETIMES WORKS
claude "start" # Worked once with inline prompt
claude /doctor # Seems more reliable

Inline prompts are not a reliable workaround. The freeze appears random but frequent, making Claude Code essentially unusable on Windows.

Steps to Reproduce

1. Open PowerShell or CMD on Windows
2. Navigate to any project directory
3. Run claude (no arguments)
4. Observe: TUI renders completely (logo, version, project path, prompt suggestions visible)
5. Hooks may execute (if configured)
6. Attempt to type anything
7. Result: No characters appear, cursor is frozen
8. Attempt Ctrl+C, Ctrl+Z, Esc
9. Result: No response, process cannot be interrupted
10. Must force-close terminal window

Expected Behavior

• Claude Code should accept keyboard input at the prompt after TUI renders
• Standard interrupt signals should work
• TUI should be responsive to input

Actual Behavior

• TUI renders visually and appears ready for input
• Hooks may execute successfully
• But keyboard input is completely dead — no characters register
• Cannot interrupt with Ctrl+C/Ctrl+Z/Esc
• Requires force-kill via closing terminal or Task Manager

Diagnostic Information

claude /doctor output (this command works):

Diagnostics
└ Currently running: native (2.1.31)
└ Path: C:\Users\<username>\.local\bin\claude.exe
└ Invoked: C:\Users\<username>\.local\bin\claude.exe
└ Config install method: native
└ Search: OK (bundled)
Updates
└ Auto-updates: enabled
└ Auto-update channel: latest
└ Stable version: 2.1.19
└ Latest version: 2.1.31
Version Locks
└ No active version locks

Environment details

• .claude.json size: 40KB (not bloated)
• .claude/ folder: Cleared during troubleshooting (was 1.35GB - 800MB projects, 400MB debug)
• Issue persists even after clearing all cached data
• Issue persists across different projects (tested multiple projects, empty test folder)
• Issue persists across different terminals (PowerShell, CMD)

Troubleshooting Already Attempted

1. ❌ Cleared ~\.claude\projects\ (800MB) - no effect
2. ❌ Cleared ~\.claude\debug\ (400MB) - no effect
3. ❌ Cleared entire ~\.claude\ folder - no effect
4. ❌ Created .claudeignore for large project - no effect
5. ❌ Tested in empty folder with no files - same freeze
6. ❌ Tested different terminals (CMD, PowerShell) - same freeze
7. ❌ Pressed Esc, Enter, Ctrl+C, clicked in window - no response
8. ❌ Launching with inline prompt - inconsistent, mostly freezes
9. ✅ claude /doctor works (but not useful for actual work)

Likely Cause

The freeze occurs in the TUI input handling layer after the application has fully loaded and rendered. When a prompt is passed inline, this input-waiting state is bypassed, which explains why inline prompts sometimes work.

Possibly related to:

• Shell snapshot/permission system (referenced in #6823)
• Windows-specific terminal input handling
• Ink/React TUI input event loop in idle state

Related Issues

• #6823 - Claude CLI randomly/predictably freezes on Windows
• #7182 - Incredibly slow performance (PowerShell freezes main thread)
• #7694 - Input is very laggy on Windows systems
• #9114 - Claude Code hangs and freezes on startup

Version Information

• Current version: 2.1.31 (latest channel)
• Stable version: 2.1.19
• Note: Unable to test stable version yet - claude update --channel stable not recognized

Workaround

No reliable workaround exists.

• Inline prompts sometimes work, sometimes freeze
• claude /doctor appears more reliable but is not a functional workaround for actual usage
• Downgrade to stable (2.1.19) untested but recommended

Impact

• Severity: Critical/Blocker - Claude Code is essentially unusable on Windows
• Affected users: Windows users on v2.1.31
• Workflow impact: Cannot use Claude Code for any work