Remote Control permanently disconnects after rate limit with multiple concurrent sessions

Problem

Remote Control / mobile connections permanently disconnect after hitting rate limits when multiple Claude Code sessions are running concurrently. The connection never recovers, even after the rate limit resets.

Environment

• Claude Code CLI: 2.1.71
• Claude Desktop App: 1.1.5368 (running claude-code 2.1.63)
• macOS (Apple Silicon, 64 GB RAM)
• Plan: Max

Setup

Running 8-10 concurrent Claude Code sessions (mix of local terminal, SSH remote, and Desktop app sessions). Some sessions have very large contexts (900+ MB memory footprint).

Reproduction

1. Have multiple Claude Code sessions running (5+)
2. Start a Remote Control session and connect from mobile (iOS app or browser)
3. Send a few messages from mobile
4. The shared per-account rate limit gets hit due to concurrent API usage across all sessions
5. The mobile/remote connection permanently disconnects
6. Even after rate limits reset, the remote connection never recovers — the session appears dead from mobile
7. Only workaround is killing and restarting the session with claude remote-control

Expected behavior

• Remote Control should gracefully pause when rate-limited and automatically resume when limits reset
• At minimum, it should display a clear "rate limited, waiting to reconnect" state rather than silently dying

Additional context

• Related to #26699 and #29219
• This makes Remote Control essentially unusable for users running multiple sessions, which is a common workflow (e.g., separate sessions per project, SSH sessions to remote machines)
• Feature request: consider per-session or per-connection rate limit awareness so that one session's rate limit hit doesn't permanently kill another session's remote connection

🤖 Generated with Claude Code