Active session becomes unresponsive after Windows resumes from hibernation

Summary

After my Windows machine wakes from hibernation, any Claude Code session that was already running becomes effectively unresponsive — typing is delayed to roughly 1 character per minute. Starting a new session works fine, and claude --resume <session-id> on the same conversation also works fine. It's specifically the already-running session that's stuck.

This happens to me every day.

Steps to reproduce

1. Start a Claude Code session and have an active conversation.
2. Hibernate the machine (close lid / system hibernate).
3. Wake the machine and return to the existing terminal with the live Claude Code session.
4. Try to type a new prompt.

Expected

The session detects the network state change on resume and reconnects, or input is responsive.

Actual

Input takes ~1 minute per character. The session never recovers on its own (I haven't waited longer than ~10 minutes).

Workaround

• Ctrl+C the hung session, then claude --resume and pick the same session — works perfectly, no context lost.
• Starting a brand new session also works.

Environment

• Claude Code: 2.1.119
• OS: Windows 11 Enterprise (10.0.26200)
• Shell: bash (Git Bash)

Related (closed) issues

These describe the same / closely related behavior but were closed as Not Planned, so I'm filing fresh:

• #32116 — Claude CLI unresponsive after laptop resume (Linux)
• #24394 — \claude --resume\ freezes on Windows
• #22204 — \/resume\ command hangs with large session history

A wake/resume detection that forces reconnect on the active session would fix this.