Rank, 14 days: 10 on the Claude Code sheet
92 people reported
All time, since Sep 18, including 57 thumbs-up on GitHub.
Remote sessions drop, never reconnect
“The app stopped all four active sessions, quit, restarted, and restored the sessions, but Remote Control was not re-established for any of them.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/themes/222/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
6 bugs in this theme
- Remote Control lost on relaunchHas a workaround61 people
- Restart orphans Remote Control sessionsHas a workaround11 people
- Remote Control sessions archived on quitNo workaround yet7 people
- Unarchived session never reconnectsNo workaround yet6 people
- Remote Control drops on idleHas a workaround6 people
- Remote Control sessions go offlineNo workaround yet4 people
What's included
- Desktop bridge closes with code 4090 at the 12-hour ingress-token refresh and stays dead until app restart
- Desktop auto-update (stealth) relaunch restores sessions without re-enabling Remote Control
- Idle Code-tab sessions lose Remote Control; re-enabling says "requires an active session. Send a message first"
- Archived then unarchived sessions stay pending/disconnected; the remote-control server never spawns a worker
- After the server or desktop app restarts, old sessions show "environment was deleted" and cannot be continued
Not included
- Remote Control failing to connect at all with HTTP 403
- Forked sessions that never register with Remote Control
- Prompts, questions, notifications or files that do not reach a connected remote client
Original reports35, newest first
- Desktop (macOS): quitting the app (manual or stealth update) archives the claude.ai copy of every Remote Control session, and nothing unarchives it#107891
- Desktop (Windows): auto-update restart turns Remote Control off for all existing sessions, with no setting to keep it on#107767
- Desktop: SSH sessions lose their Remote Control link after an app restart until used on the host computer#107766
- [Desktop] Remote Control is not restored on existing local sessions after the app's automatic (stealth) update#107253
- Desktop app (Windows) restarts unattended; idle Code sessions lose Remote Control and can't be re-enabled remotely#105690
- Desktop: Remote Control transport dies on 4090 conflict and never recovers; auto-update relaunch leaves it off while session still reports "on"#105563
- Desktop (macOS): Remote Control for local Code sessions is not restored after silent auto-update relaunch#104230
- Desktop app (Windows): Remote Control is not restored for a session after the app's silent auto-update relaunch#104206
- Remote Control: unarchived session is never re-adopted by the running server#104142
- macOS desktop: Remote Control not restored when a Code-tab session goes idle — session vanishes from iOS app until a message is sent on the Mac#103872
Show all 35Show only the newest 10
- Desktop app: a Code session reopened after an app relaunch comes back with Remote Control off, despite "Connect new sessions to Remote Control"#103826
- [Desktop] Auto-update restart archives active Remote Control sessions and does not restore them#103005
- Desktop: Remote Control drops on every idle session and can't be re-enabled until a message is sent from the Mac#102534
- Remote Control: session shows "environment was deleted" after server exit; no way to re-attach to a new environment#101190
- Desktop app (Windows): Remote Control bridge never re-arms after an app restart/auto-update — session goes silent on mobile for hours and shows as archived, until the user types in the desktop app#100940
- Desktop app: Remote Control is not re-attached to existing Code sessions after the automatic (stealth) update relaunch#100694
- Desktop: Remote Control is not restored after app update/restart for existing sessions, and sessions silently disappear from mobile while the app still reports "connected"#100590
- Windows: MSIX auto-update force-terminates Claude Desktop, killing active Code tab sessions and Remote Control (~every 2 days, not restored on relaunch)#100576
- claude remote-control server gets a new environment id on most restarts, so routines pinned to it die#100528
- Windows desktop: Remote Control not restored after app relaunch (silent update / restart), sessions show as archived on mobile#100114
- [Desktop] Auto-update relaunch drops all Remote Control sessions and they don't reconnect until opened locally#100106
- Idle auto-update stops all sessions and Remote Control never comes back after the relaunch#99585
- Remote Control: unarchived bridge session never reconnects (stuck "Connecting", host never spawns a worker)#99511
- Remote Control session disappears from the mobile Code#98879
- Remote Control: session on my PC becomes permanently unreachable (environment_deleted) after the desktop app was closed for a few hours#98583
- Bug: Remote Control doesn't survive app restarts or session eviction (Claude desktop, macOS)#98504
- Desktop (macOS): sessions-bridge dies at the 12-hour ingress-token refresh (code 4090), and Remote Control sessions stay offline until the app restarts#98446
- Remote Control: unarchived server-mode sessions are never re-dispatched to the running host — messages hang at "Sending…", then "Claude Code on <machine> is offline"#98310
- Remote Control: --no-create-session-in-dir never writes bridge-pointer.json, so every restart rotates the environment and kills its live sessions#96346
- Auto-update force-quits the working desktop app again: session child processes killed (exit 127), Remote Control dropped, app unlaunchable until reboot - why is there still no user-chosen update timing?#96279
- Desktop app turns off Remote Control on all Code sessions after every restart/auto-update; can't be re-enabled automatically#96220
- Remote Control is not restored for sessions killed by a stealth auto-update#95491
- Desktop app: Remote Control on a running session is dropped by every app relaunch (auto-update) and only restored on the next user message; deleting another session also switched it off#95407
- Desktop auto-update ("stealth update") quits and relaunches the app while the user is away, dropping every Remote Control session#95364
- Desktop (Windows): Remote Control is not restored after the app restarts for an auto-update, so idle sessions get paused and become unreachable#95296