{"version":"2.1.227","anchor":"liveness-probing-for-remote-sessions","canonical_anchor":"liveness-probing-for-remote-sessions","heading":"Liveness probing for remote sessions","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/liveness-probing-for-remote-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Liveness probing for remote sessions\n\nRemote sessions can detect a dead connection through probes and force a reconnect, off by default.\n\n**What**\n\nRemote 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.\n\n**Details**\n\n- Logs `cli_sse_liveness_probe_received` on each probe and `cli_sse_liveness_probe_handler_threw` if handling one fails.\n- Success and failure counters are recorded as `ccr_liveness_probe`.\n- None of this machinery existed in 2.1.226.\n\n**Evidence**\n\n`supports_liveness_probe`, `liveness_probe`, `cli_sse_liveness_probe_received`\n\n- Flag `tengu_ccr_idle_heartbeat`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.227; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}