Input completely frozen when resuming session with --continue/--resume on Windows

Description

When starting Claude Code with the --continue or --resume flag to resume a previous session, the terminal becomes completely unresponsive. No text input, slash commands, or Esc key presses are registered. The only way to recover is to kill the terminal window.

This has occurred twice (Feb 6 and Feb 7, 2025). I have not observed this on fresh sessions.

Steps to reproduce

1. Have a previous Claude Code session in a project
2. Run claude --continue or claude --resume to resume/pick a session
3. Terminal launches but input is completely frozen

Expected behavior

Session resumes (or session picker appears) and accepts input normally.

Actual behavior

• Cannot type any text
• Cannot use / commands
• Esc key does not work
• Ctrl+C does not break out
• Must kill the terminal window to recover
• With --resume, the session picker list appears but cannot be interacted with (no keyboard input registered)

Environment

• Claude Code version: 2.1.37
• OS: Windows
• Node.js: v22.17.0
• npm: 11.6.0
• MCP servers: Claude-in-Chrome extension

Additional context

• Happens with both --continue and --resume, not on fresh sessions
• With --resume, the session list renders but keyboard input is frozen so no session can be selected
• MCP server (Claude-in-Chrome) is configured and may be relevant if reconnection during session restore is involved
• Unsure if the previous sessions had any particular state (large context, pending tool calls, etc.) that could trigger this