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.
tengu_bridge_selfheal_heartbeats On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.222: 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.
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
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: tengu_bridge_selfheal_heartbeats