Remote sessions gain reconnect and reactivation heartbeats plus stale-connection recovery, all off here.
Three remote-control behaviours sit behind gates that all fall back to false.
tengu_ccr_reconnect_beat 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.228: 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.
tengu_ccr_reactivation_beat 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.228: 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.
tengu_bridge_recover_stale_epoch Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.228: 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.228. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Three new remote-control behaviours were added behind server-side flags: a beat on reconnect (tengu_ccr_reconnect_beat), a beat on reactivation (tengu_ccr_reactivation_beat) and recovery from a stale connection epoch (tengu_bridge_recover_stale_epoch). All three fall back to false in this build, so they are on only if server config says so.
- The client's liveness option was renamed to advertise heartbeat-probe support.
- An idle tracker is now passed into the client and fed by user-driven inbound traffic: user messages from the remote worker, successful control responses, and bash commands.
tengu_ccr_reactivation_beat
Strings lifted out of the shipped bundle, so the claim above can be checked against them.