[BUG] `claude -c` and `claude --resume <session-id>` freeze on Windows - input completely unresponsive after session loads

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Summary

claude -c (and claude --continue) and claude --resume <session-id> freeze completely on Windows after loading the previous session. The session content loads and displays correctly, but the input field becomes completely unresponsive — no typing, no Ctrl+C, nothing works. The only way to exit is force-killing the process via Task Manager.

However, claude --resume (interactive picker without session ID) works perfectly fine and allows normal input after loading the same session.

Environment

• Claude Code version: 2.1.37 (latest)
• OS: Windows 11
• Terminal: PowerShell 7.5.4
• Plan: Claude Max (Opus 4.6)
• Installation*: Native installer (not npm)

Steps to Reproduce

1. Open PowerShell
2. Run claude in any directory
3. Type hello, get a response
4. Run /exit to quit normally
5. Run claude -c
6. Session loads correctly (previous messages displayed)
7. Input is completely frozen — cannot type anything, Ctrl+C does not work
8. Must force-kill process from Task Manager

What Works vs What Doesn't

| Command | Result |
|---------|--------|
| claude (new session) | ✅ Works |
| claude --resume (interactive picker) | ✅ Works |
| claude -c / claude --continue | ❌ Freezes after loading session |
| claude --resume <session-id> | ❌ Freezes after loading session |

Troubleshooting Already Attempted

• Killed all Claude processes before retrying
• Deleted $env:USERPROFILE\.claude\projects, sessions, and .lock files
• Tested in a completely different/clean directory (not a project folder) — same result
• Confirmed this is NOT directory-specific — happens globally
• Tried claude -c --verbose — session loads with token count (24547 tokens) but input still frozen

Related Issues

• #7426 — claude --continue freezes
• #7455 — Freezing issues with --continue and --resume after Ctrl+C on Windows

What Should Happen?

claude -c and claude --resume <session-id> should load the previous session AND allow normal text input, just like claude --resume (interactive picker) does. All three methods should behave consistently.

Error Messages/Logs

No error messages produced. The session loads successfully (previous messages displayed, token count shown as 24547 tokens in verbose mode), but the terminal input becomes completely unresponsive. No crash, no error output — just a silent input freeze.

Steps to Reproduce

1. Open PowerShell 7.5.4 on Windows 11
2. cd to any directory (tested on both project and clean directories)
3. Run claude
4. Type hello and receive a response
5. Type /exit to quit normally
6. Run claude -c
7. Observe: session loads correctly, previous messages are displayed
8. Try to type anything — input is completely frozen, no characters appear
9. Ctrl+C does not work — must force-kill via Task Manager

Alternative reproduction with --resume:

1. After step 5, note the session ID from the output
2. Run claude --resume <session-id>
3. Same freeze behavior occurs

Working workaround:

1. Run claude --resume (without session ID)
2. Select the session from the interactive picker
3. Input works normally

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.29

Claude Code Version

2.1.37 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

PowerShell 7.5.4