End-to-end liveness probing for remote workers is built but its advertising flag falls back to off.
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.
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