Idle liveness probe support in the remote bridge is behind a flag that falls back to off.
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.
tengu_ccr_idle_heartbeat 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.227: 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.227. 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_ccr_idle_heartbeat