{"version":"2.1.248","anchor":"resumed-bridge-sessions-drain-instead-of-replaying","canonical_anchor":"resumed-bridge-sessions-drain-instead-of-replaying","heading":"Resumed bridge sessions drain instead of replaying","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/resumed-bridge-sessions-drain-instead-of-replaying","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Resumed bridge sessions drain instead of replaying\n\nRestarting the remote bridge no longer replays sessions that already reconnected.\n\n**What**\n\nEach session the remote-control bridge picks up is removed from its saved active list as it is serviced, so a restart does not replay sessions that already reconnected. Warnings about not being able to reuse the previous environment are now suppressed when resuming one specific session.\n\n**Details**\n\n- The removal rewrites the pointer file through the serializing write queue.\n- Startup registers print-mode signal handling before installing the SIGINT, SIGTERM and SIGHUP handlers.\n- Suppressed message: \"Warning: Could not reuse the previous environment. Existing claude.ai\/code sessions from the previous run will not reconnect.\"\n\n**Evidence**\n\n`Warning: Could not reuse the previous environment. Existing claude.ai\/code sessions from the previous run will not reconnect.`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}