{"version":"2.1.307","anchor":"remote-control-stream-renewal-no-longer-special-cases-transp","canonical_anchor":"remote-control-stream-renewal-no-longer-special-cases-transp","heading":"Remote-control connections now renew the same way for every session","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/remote-control-stream-renewal-no-longer-special-cases-transp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Remote-control connections now renew the same way for every session\n\nRenewing a remote-control stream now always waits for a quiet moment when a worker connection exists, whatever kind of connection it is\n\n**What**\n\nWhen a session is controlled remotely, Claude Code keeps a stream open to receive messages and renews it from time to time. It now always renews that stream. If a separate worker connection exists, it waits until that connection is quiet first; if not, it renews straight away. Before, it only waited for one particular kind of worker connection. The early stop in the resync step after a reconnect was also removed, so that step now runs through.\n\n**Why**\n\nReconnecting and catching up after a dropped connection now behaves differently for sessions that have a worker connection.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}