Desktop app: Remote Control is not re-attached to existing Code sessions after the automatic (stealth) update relaunch
App: Claude desktop app for macOS, version 2.31226.0 (Code tab / Claude Code sessions)
Machine: Apple Silicon Mac laptop, macOS 27.0
Date: 2026-10-09 13:07 JST (04:07 UTC)
What happened
A long-running Code session had Remote Control turned on and was being followed from claude.ai/code and the mobile app. While the user was away from the keyboard, the app performed its automatic background update relaunch ("stealth update after idle timeout"). The app stopped all four active sessions, quit, restarted, and restored the sessions, but Remote Control was not re-established for any of them. From the phone the session simply went dark; the local session kept working. Remote Control came back only when it was turned on again manually about 26 minutes later.
The same relaunch has happened on 2026-10-02, 10-06, 10-07, 10-08 and 10-09 (five times in eight days), so this is a recurring loss of the remote link rather than a one-off.
Log excerpts (~/Library/Logs/Claude/main.log)
13:06:45 [info] [updater] Staged version 2.31226.0 is still current (latest: 2.31226.0, lastTarget: null)
13:07:14 [info] [stealth-update] Triggering stealth update after idle timeout
13:07:14 [info] [CCD] Stopping 4 active session(s) on quit
13:07:16 [info] [CCD] CLI exit before update: 4 of 4 exited within 1468ms
13:07:16 [info] beforeQuitForUpdate handler fired, going down for update
13:07:16 [info] Running onQuitCleanup: remote-control-serve
13:07:24 [info] [rc-serve] started (details in remote-control.log)
13:33:29 [info] Enabling remote control for session local_<id> <- manual re-enable
13:33:30 [info] [remote-control] bridge_state: "ready"
13:33:31 [info] [remote-control] bridge_state: "connected"~/Library/Logs/Claude/remote-control.log right after the relaunch:
13:07:14.934 quit: 0 attached session(s) queued for unarchive, 0 parked for the next launch
13:07:24.395 start … persistedFolders=0 pendingDelete=0 pendingUnarchive=0
13:07:24.924 state pending → pending trigger=launch intent=default served=3 registering=0 failed=0 excluded=0 limited=0 missing=1 sessions=0
13:07:25.024 state pending → off trigger=gate intent=default served=3 … sessions=0So at quit no attached session was parked for the next launch, and after the relaunch the Remote Control server saw sessions=0 and gated itself off, although "Connect new sessions to Remote Control" is On and the session had Remote Control on before the relaunch.
Expected
Sessions that had Remote Control on before an automatic update relaunch should be re-attached after the relaunch (or the relaunch should be deferred while a session is linked to Remote Control and the user is away), so that a user following from the phone does not lose the link without any notice.
Comparison
The OpenAI Codex desktop app on the same Mac keeps its remote connection across its own updates, so a relaunch that preserves the remote link is achievable.
Settings at the time
- Connect new sessions to Remote Control: On
- Keep computer awake while Claude works: On (the Mac did not sleep;
pmset -g logshows no sleep event) - Session permission mode: auto; session was running (not idle) but the user had no keyboard activity
🤖 Generated with Claude Code