[BUG] Remote Control session silently dies after 529 error — no error shown, stuck on idle, no timeout

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?

When a Remote Control session encounters a 529 (overloaded) API error, the session silently becomes unresponsive. The mobile/web client continues to show the session as “idle” with no error message, no timeout notification, and no indication that the session is dead. Users are left waiting indefinitely with no way to distinguish between a healthy idle session and a dead one.

What Should Happen?

When a 529 error occurs during a Remote Control session, the client should:

1. Display a clear error message (e.g., "API overloaded, retrying..." or "Session disconnected")
2. Auto-retry the request, or clearly indicate the session has died
3. Show a timeout notification if no response is received after a reasonable period
4. Never show "idle" status for a dead/unresponsive session

Error Messages/Logs

Steps to Reproduce

1. Start a Remote Control session: claude remote-control
2. Connect from mobile via claude.ai/code
3. Send a task to Claude — it begins working normally
4. A 529 (overloaded) API error occurs mid-task
5. The session freezes mid-response and status shows "idle"
6. Sending new messages from the mobile client gets no response and no error
7. No timeout, no error notification — session appears alive but is completely unresponsive

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.78（claude code）

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_