A remote connection with failing heartbeats now rebuilds itself instead of hanging on a half-dead socket.
tengu_bridge_selfheal_heartbeats Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.222: off
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.
Read once, for one account on one subscription tier, against v2.1.222. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The 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.
- close code 4093 has its own recovery entry reporting
reconnectingDetail: "presence heartbeats failing — reconnecting" - a successful rebuild emits the presence code
recovered_heartbeat_4093 - gated on tengu_bridge_selfheal_heartbeats whose in-source fallback is true, so absent a remote value it runs
- additionally requires !outboundOnly
[bridge:repl] CCR v2: heartbeats failing while SSE healthy — closing for transport rebuild
Strings lifted out of the shipped bundle, so the claim above can be checked against them.