{"version":"2.1.222","anchor":"remote-bridge-presence-heartbeats-can-self-heal-the-transpor","canonical_anchor":"remote-bridge-presence-heartbeats-can-self-heal-the-transpor","heading":"Remote-bridge presence heartbeats can self-heal the transport","tier":"notice","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/remote-bridge-presence-heartbeats-can-self-heal-the-transpor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Remote-bridge presence heartbeats can self-heal the transport\n\nRemote sessions now rebuild a stuck connection when heartbeats keep failing but data still flows.\n\n**What**\n\nThe v2 remote-control transport now counts consecutive presence heartbeat failures and, when heartbeats keep failing while the SSE read stream still looks alive, closes with a new code 4093 and rebuilds the transport rather than sitting on a dead connection.\n\n**Details**\n\n- New close code 4093 with human-readable reason text explaining that presence heartbeats to the server kept failing.\n- New internals: resetHeartbeatStreak, onHeartbeatLost, and isReadStreamRecentlyAlive, which is what distinguishes a stalled heartbeat from a genuinely dead read stream.\n- Gated on tengu_bridge_selfheal_heartbeats; the fallback value in source is true, with the real value coming from remote config.\n- Skipped entirely when the session is outboundOnly.\n\n**Evidence**\n\n`presence heartbeats to the server kept failing (code 4093)`\n\n- Flag `tengu_bridge_selfheal_heartbeats`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.222; this account: on, anonymous baseline: on, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Bridge\n- Names: `tengu_bridge_selfheal_heartbeats`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}