Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.228 ·

Remote-control heartbeat and stale-epoch recovery, all off

Remote sessions gain reconnect and reactivation heartbeats plus stale-connection recovery, all off here.

Nothing to try yet In Development
JSON All of v2.1.228
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
In DevelopmentKind: in v2.1.228,
In DevelopmentSection of the release

Three remote-control behaviours sit behind gates that all fall back to false.

What

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.

Details
  • 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.
Evidence

tengu_ccr_reactivation_beat

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_ccr_reconnect_beat Off by default, switched on for this account

The 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.228: 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.

tengu_ccr_reactivation_beat Off by default, switched on for this account

The 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.228: 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.

tengu_bridge_recover_stale_epoch Not enough to say

Nothing 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: 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.228. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_ccr_reactivation_beat, read as this 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.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_ccr_reactivation_beat, read as this 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.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_bridge_recover_stale_epoch

See this entry in the whole of v2.1.228 →

Feedback