{"version":"2.1.222","anchor":"remote-control-bridge-heals-a-socket-whose-heartbeats-keep-f","canonical_anchor":"remote-control-bridge-heals-a-socket-whose-heartbeats-keep-f","heading":"Remote-control bridge heals a socket whose heartbeats keep failing","tier":"notice","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/remote-control-bridge-heals-a-socket-whose-heartbeats-keep-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Remote-control bridge heals a socket whose heartbeats keep failing\n\nA remote connection with failing heartbeats now rebuilds itself instead of hanging on a half-dead socket.\n\n**What**\n\nThe CCR v2 transport now spots heartbeats failing repeatedly while the SSE read stream still looks healthy, and closes the socket with code 4093 so the bridge rebuilds the transport instead of sitting on a half-dead connection.\n\n**Details**\n\n- close code 4093 has its own recovery entry reporting `reconnectingDetail: \"presence heartbeats failing \u2014 reconnecting\"`\n- a successful rebuild emits the presence code `recovered_heartbeat_4093`\n- gated on tengu_bridge_selfheal_heartbeats whose in-source fallback is true, so absent a remote value it runs\n- additionally requires !outboundOnly\n\n**Evidence**\n\n`[bridge:repl] CCR v2: heartbeats failing while SSE healthy \u2014 closing for transport rebuild`\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"}