{"version":"2.1.305","anchor":"bridge-heartbeat-now-targets-only-sessions-that-are-due","canonical_anchor":"bridge-heartbeat-now-targets-only-sessions-that-are-due","heading":"Bridge connection sends keep-alive signals only for sessions that are due","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/bridge-heartbeat-now-targets-only-sessions-that-are-due","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Bridge connection sends keep-alive signals only for sessions that are due\n\nThe bridge now sends keep-alive signals only for sessions that are due one, rather than for all sessions at once\n\n**What**\n\nA heartbeat is a regular signal that tells the other side a session is still alive. In the bridge's polling loop, Claude Code now works out which sessions are due a heartbeat, leaves out those that are waiting after a recent failure, and sends heartbeats only for the rest. It then follows up on any due sessions that were left out. Before, one check decided whether to send a single heartbeat for every session.\n\n**Why**\n\nWith several sessions open, this can cut down on keep-alive signals that were not needed.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}