{"version":"2.1.248","anchor":"remote-control-bridge-remembers-active-sessions-across-resta","canonical_anchor":"remote-control-bridge-remembers-active-sessions-across-resta","heading":"Remote-control bridge remembers active sessions across restarts","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-control-bridge-remembers-active-sessions-across-resta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote-control bridge remembers active sessions across restarts\n\nThe remote-control bridge saves its active sessions and picks them back up after a restart.\n\n**What**\n\n`claude remote-control` now saves the session IDs it is currently servicing when it shuts down for an upgrade, reload or yield, and re-queues them on the next start. Sessions survive a restart instead of being dropped.\n\n**Details**\n\n- The IDs and a timestamp are stored in the bridge pointer file, capped by `MAX_POINTER_ACTIVE_SESSION_IDS`.\n- They are only re-queued if the stamp is still within `PERSISTED_SESSION_RESUME_WINDOW_MS`.\n- Pointer writes are serialized through a write queue; clearing the pointer stops the hourly refresh, which now also drops stale session lists.\n- Only applies to runs that own the pointer and preserve state on shutdown.\n\n**Evidence**\n\n`persistActiveSessionsOnShutdown`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}