Remote bridge self-heals when heartbeats fail but SSE is alive / Claude Code v2.1.222

You'll notice

Useful2 Signal0

Remote Bridge not in their notes

The remote bridge tears down half-dead sessions so the connection rebuilds instead of hanging.

Feature flag

tengu_bridge_selfheal_heartbeats Off by default, switched on for this account

The 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

tengu_bridge_selfheal_heartbeats

What

The v2 remote bridge can now detect the case where heartbeats keep failing while the SSE read stream is still delivering data, and tears the session down so the transport is rebuilt instead of sitting in a half-dead state.

Details

Session state tracks consecutiveHeartbeatFailures and heartbeatStreakStartedAtMs, plus a new onHeartbeatLost callback.
Liveness is judged by a new isReadStreamRecentlyAlive() helper backed by lastLivenessEvidenceAtMs.
On trigger the session closes with code 4093 and logs "[bridge:repl] CCR v2: heartbeats failing while SSE healthy — closing for transport rebuild".
Wired through a selfHealHeartbeats option read from the tengu_bridge_selfheal_heartbeats gate, whose fallback is true; the real value comes from remote config.

Evidence

tengu_bridge_selfheal_heartbeats

Strings lifted out of the shipped bundle, so the claim above can be checked against them.