[BUG] Session hangs indefinitely after being idle — message never sent/received

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?

After leaving the desktop app idle for a while (e.g. ~10-30+ min away from the computer), sending a new message results in an infinite hang. The message is typed and submitted, but no response ever comes back, no error appears, and the "thinking" spinner just counts elapsed time indefinitely (observed at 18s, 35s+). The only way to recover is to close the session and start a new one.

What Should Happen?

The app should detect the stale/dropped connection after idle and either automatically reconnect and retry, or show a clear "connection lost" state — instead of hanging silently forever.

Error Messages/Logs

No error message appears — that's part of the bug. It fails silently.

Steps to Reproduce

1. Have an active Claude Code desktop session with conversation history.
2. Leave the app idle for an extended period (~10-30+ min, e.g. stepping away from the computer).
3. Return and type any new message (e.g. "ola"), press Enter.
4. Observe: message appears sent, but the spinner runs indefinitely with no response, error, or reconnect indicator.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude for Windows - Versão 1.32352.0 (e33b9a)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

Note: version shown is from the Claude for Windows desktop app's "About" screen (Help > About), since this is not the CLI — claude --version doesn't apply here.