[BUG] "Interactive mode freezes on Windows - no input response after initial setup"

Resolved 💬 15 comments Opened Sep 4, 2025 by xBOBxSAGETx Closed Sep 19, 2025

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.105 (Claude Code)
  • Operating System: Windows 10.0.26100.4946
  • Terminal: Command Prompt, PowerShell, Windows Terminal (all tested)

Bug Description

Interactive mode becomes completely unresponsive after initial setup. After accepting permissions and reaching the main Claude Code interface, the terminal freezes and no longer accepts any input. The interface appears functional (shows welcome message and input field) but is completely non-interactive. This renders the primary Claude Code workflow (drag-and-drop files, interactive sessions) unusable.

Steps to Reproduce

  1. Install Claude Code using either npm install -g @anthropic-ai/claude-code or native Windows installer
  2. Navigate to project directory: cd /d "C:\path\to\project"
  3. Run claude command
  4. Accept security permissions (choose option 1: "Yes, proceed")
  5. Wait for main interface to load with welcome message and input field
  6. Attempt to type any command or input

Expected Behavior

After accepting permissions, the Claude Code interface should be fully interactive, allowing users to:

  • Type commands and questions
  • Drag and drop files for analysis
  • Navigate through multi-turn conversations
  • Use all interactive features as designed

Actual Behavior

The interface loads and displays correctly but becomes completely unresponsive to input:

  • Cursor appears in input field but typing produces no visible text
  • Keyboard shortcuts (Tab, Ctrl+L, etc.) have no effect
  • Drag and drop functionality is non-functional
  • Only way to exit is by closing the entire terminal window
  • Interface appears visually correct but is entirely frozen

Additional Context

Extensive troubleshooting attempted:

  • Multiple installation methods: npm global install, native Windows installer, migration between methods
  • Multiple terminal environments: Command Prompt, PowerShell, Windows Terminal
  • Administrator privileges tested
  • Various compatibility flags attempted: --no-color, --permission-mode bypassPermissions
  • PATH configuration verified and corrected multiple times

Key findings:

  • claude --version and claude --help work correctly
  • claude -p "prompt" mode works perfectly (non-interactive)
  • Issue appears related to stuck Bun processes (observed via Task Manager)
  • Interactive mode works briefly if started from specific project directories but fails consistently in new terminals
  • Problem persists across clean reinstalls and different installation methods

Working workaround:
Non-interactive mode (claude -p "prompt") functions correctly, but this eliminates core functionality like file uploads, drag-and-drop, and multi-turn conversations.

Impact:
This completely blocks the intended Claude Code workflow for users who need to upload large files or work iteratively with their codebase. The issue makes Claude Code essentially unusable for its primary use case on Windows systems experiencing this bug.

System specifications:

  • Node.js: v22.18.0
  • npm: 10.9.3
  • Windows Terminal: Latest version
  • No unusual terminal enhancement software installed

View original on GitHub ↗

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