Interactive mode freezes on second launch in non-home directories (Windows)

Resolved 💬 4 comments Opened Feb 6, 2026 by bradstamp-bramon001 Closed Mar 6, 2026

Bug Description

Claude Code interactive mode freezes (accepts no keyboard input) on the second and all subsequent launches in any directory except the user's home directory (C:\Users\<user>). The first launch in a new directory always works. The home directory always works regardless of how many times you launch.

Environment

  • Claude Code: 2.1.33 (npm install via @anthropic-ai/claude-code)
  • OS: Windows NT 10.0.26200.0 (Windows 11)
  • Node.js: v22.20.0
  • npm: 10.9.3
  • PowerShell: 5.1
  • Terminal: Windows Terminal (PowerShell and cmd both affected)

Steps to Reproduce

  1. mkdir C:\test-fresh && cd C:\test-fresh
  2. claudeworks (first launch, shows trust prompt, REPL is interactive)
  3. Exit with /exit
  4. claudefrozen (REPL appears but no keyboard input accepted)

What Was Ruled Out (24 tests across 3 sessions)

| Suspect | Result |
|---------|--------|
| .mcp.json (project or global) | NOT the cause — freeze occurs with no .mcp.json present |
| CLAUDE.md | NOT the cause — bare directories freeze too |
| F: drive / non-C: paths | NOT the cause — C:\test-fresh also freezes |
| Git repos | NOT the cause — non-git directories freeze too |
| Project size | NOT the cause — empty directories freeze |
| Session cache (~/.claude/projects/<path>/) | Clearing does NOT fix it |
| All session files (debug, todos, session-env) | Clearing does NOT fix it |
| history.jsonl | Renaming does NOT fix it |
| --strict-mcp-config --setting-sources user | Does NOT fix it |
| Reboot | Does NOT fix it |
| npm vs native binary | Both freeze identically |
| Junction links (C: pointing to F:) | Does NOT fix it (resolves to real path) |

Theory

The first launch shows a workspace trust/permission prompt which likely uses simple input handling. Subsequent launches skip the trust prompt and go directly to the REPL, which uses Ink's raw mode — suspected to be broken on Windows in this scenario. The home directory may have special handling that bypasses this code path.

Workarounds

  1. Launch from home directory: cd ~; claude --add-dir F:\project (works but doesn't load project CLAUDE.md or .mcp.json)
  2. Non-interactive mode: claude -p "prompt" works from any directory
  3. VS Code extension (untested but may avoid the terminal issue)

Related Issues

  • #10487 — Permission prompt unresponsive on Windows non-home directories
  • #9929 — Interactive mode completely frozen on Windows 11 - Raw mode not supported
  • #7171 — Interactive mode freezes on Windows
  • #12234 — Claude Code freezes intermittently on Windows Terminal
  • #18109 — Claude Code hangs indefinitely on Windows PowerShell

View original on GitHub ↗

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