Bug: Remote Control doesn't survive app restarts or session eviction (Claude desktop, macOS)

App versions: Claude 2.9939.x → 2.16120.0 (auto-updated during the period below)
Machine: macOS, 24 GB RAM, sleep disabled (Claude holds a NoIdleSleep assertion)
Setting: the Remote Control default for new sessions is ON

What happens

Local Code sessions with Remote Control on disappear from the Claude mobile app and claude.ai/code without the user doing anything. From the phone they look archived. In the desktop app they're still listed as active, but Remote Control is off.

Expected

A session that had Remote Control on should reconnect automatically when:

• the app relaunches (including auto-update relaunches), and
• a paused or evicted session is resumed.

The session should stay reachable from the phone, or at least be restartable from there.

What the logs show (~/Library/Logs/Claude/main.log)

1. App quits and relaunches stop all sessions, and Remote Control isn't restored. There were 7 quit/relaunch events between Sep 25 and 29, 2026, including an update relaunch on 2026-09-28 at 15:06 after 2.9939.4 downloaded.

``
[CCD] Stopping 8 active session(s) on quit
`
Afterwards, Remote Control had to be switched on again by hand for each session. One re-enable failed:
`
2026-09-29 10:30:52 [error] Failed to toggle remote control for local_fb28892b-…: "Couldn't reconnect to your Remote Control session. Retry, or start a fresh session without --resume."
2026-09-29 10:26:47 [error] Failed to toggle remote control for local_80998e20-…: "Session creation failed — see debug log"
``

1. The session governor's evictions silently drop Remote Control.

``
[CliGovernor] at cap=8; evicting local_3ceee273-… (idle 285s) for warm spawn
[CCD] Pausing session local_3ceee273-… (governor_evict)
[CliGovernor] memory pressure (warning): evicted 1 of 1 idle session(s)
``

1. Idle disconnects:

``
[WarmLifecycle:preview] Idle timeout reached, disconnecting local_3ceee273-…
``

1. A stopped session can't have Remote Control turned back on until it runs a turn on the Mac. Enabling it returns:

> "Remote Control requires an active session. Send a message first."

So a user who is away from the Mac can't get the session back from the phone at all.

Suggestions

• Persist each session's Remote Control state and re-establish it after a relaunch or update.
• Exempt Remote Control sessions from governor eviction, or keep a lightweight presence so they stay listed and can be woken from the phone.
• Let the phone wake a stopped local session instead of hiding it.