Claude Code v2.1.69 native binary TUI hangs on Windows (all terminals)

Resolved 💬 3 comments Opened Mar 5, 2026 by cletus424 Closed Apr 3, 2026

Description

After the switch from npm to native .exe installer (v2.1.69, built 2025-03-04), running claude interactively hangs on Windows. The TUI renderer never appears. This affects all terminals (CMD, Git Bash, Windows Terminal) — not just CMD.

Claude Code still works when launched as a subprocess (e.g., from Claude Desktop app or via claude -p), confirming the issue is specifically with the interactive TUI renderer in the native binary.

Environment

  • OS: Windows 11 Pro 10.0.26200
  • Terminal: CMD, Git Bash — both hang
  • Claude Code version: 2.1.69
  • Node.js: v22.20.0
  • Binary location: %USERPROFILE%\.local\bin\claude.exe (PE32+ native binary, ~235MB)

Steps to Reproduce

  1. Open any terminal on Windows (CMD, Git Bash, PowerShell, etc.)
  2. Run claude
  3. Process starts but hangs — no TUI is rendered

Expected Behavior

Claude Code should launch the interactive TUI, as it did with the previous npm-based installation.

Workarounds

  • claude -p "prompt" works (non-interactive, one-shot mode)
  • Claude Code works when invoked as a subprocess from Claude Desktop app
  • No workaround exists for interactive terminal sessions on Windows

Additional Context

  • The previous npm-installed version worked correctly in all terminals
  • This regression coincides with the migration from npm package to native Windows installer
  • The npm global package is no longer installed (npm list -g shows empty)

View original on GitHub ↗

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