The remote bridge can support idle liveness probes and resync on reconnect, off by default.
Idle liveness probe support in the remote bridge is behind a flag that falls back to off.
tengu_ccr_idle_heartbeat 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.227: 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.227. 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 remote bridge can tell the server it supports idle liveness probes, gated on tengu_ccr_idle_heartbeat, which falls back to off. When enabled, a probe triggers an immediate heartbeat and a reconnect triggers a resync.
- Advertisement is
advertiseLivenessProbeSupport; the session wiressetOnLivenessProbeandsetOnReconnected. - Separately and not gated: proactive and recovery credential refreshes now stop early if the session has been replaced, logging
[remote-bridge] Proactive refresh skipped: session supersededand reporting outcomeskipped_superseded.
advertiseLivenessProbeSupport: Hn(),
Strings lifted out of the shipped bundle, so the claim above can be checked against them.