Desktop: stealth update relaunch does not restore Remote Control on restored sessions

Status Open
Reported on v2.1.293
Maintainer reply None cached
Activity 0 comments · opened Oct 9, 2026

Desktop app: stealth update relaunch does not restore Remote Control on restored sessions

Environment: Claude desktop app (macOS, arm64), app 2.26454.2 → 2.31226.0, bundled Claude Code 2.1.293. Session was a local Code-tab session with Remote Control on.

What happened: The desktop app applied a staged update by quietly quitting and relaunching after an idle timeout. It stopped all five running sessions and restored them on relaunch, but the Remote Control link of the session that had it on was not re-established. From the phone this looked like the session timing out; it stayed unreachable for ~2.5 h until the toolbar switch was flipped again.

Expected: A session that had Remote Control on before the stealth relaunch should come back with Remote Control on.

Log (~/Library/Logs/Claude/main.log, times local):

08:29:43 [info] Enabling remote control for session local_83af82a8-…
08:29:45 [info] [remote-control] bridge_state: "connected"
17:10:44 [info] [updater] Staged version 2.31226.0 is still current (latest: 2.31226.0, lastTarget: null)
17:11:14 [info] [stealth-update] Triggering stealth update after idle timeout
17:11:14 [info] [stealth-relaunch] Saved navigation history (21 entries, active=20)
17:11:14 [info] [CCD] Stopping 5 active session(s) on quit
17:11:14 [info] Stopping session local_83af82a8-…
17:11:15 [info] [CCD] CLI exit before update: 5 of 5 exited within 1133ms
17:11:22 [info] [CCD] Initialized with version 2.1.293
17:11:22 [info] [updater] Version changed since last launch: 2.26454.2 → 2.31226.0
17:11:22 [info] [stealth-relaunch] Version changed since the last launch: loading the saved page instead of restoring history
17:11:24 [info] [sessions-bridge] Reconnecting persisted session cse_…
   (no "Enabling remote control" / bridge_state line for local_83af82a8-… after the relaunch)
19:36:08 [info] Enabling remote control for session local_83af82a8-…   <- manual re-enable
19:36:10 [info] [remote-control] bridge_state: "connected"

Between 08:29 and 17:11 there were no bridge_state changes, so the link was healthy until the relaunch.

Notes: "Connect new sessions to Remote Control" was unset at the time. Whether setting it would cover sessions restored by a relaunch is unclear from the behaviour; either way the pre-relaunch per-session state seems the right thing to restore.

View original on GitHub ↗