Remote sessions can detect a dead connection through probes and force a reconnect, off by default.
End-to-end liveness probing for remote workers is built but its advertising flag 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?
Remote worker sessions gain an end-to-end liveness check: the heartbeat can advertise supports_liveness_probe with the current interval, the event stream recognises a liveness_probe event, and a timer forces a reconnect when probes stop arriving. Advertising defaults to off in the client, and the SDK path gates it on tengu_ccr_idle_heartbeat, which falls back to off, so no build here turns it on by default.
- Logs
cli_sse_liveness_probe_receivedon each probe andcli_sse_liveness_probe_handler_threwif handling one fails. - Success and failure counters are recorded as
ccr_liveness_probe. - None of this machinery existed in 2.1.226.
supports_liveness_probe, liveness_probe, cli_sse_liveness_probe_received
Strings lifted out of the shipped bundle, so the claim above can be checked against them.