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 ·

Idle tracking and a reactivation heartbeat for remote sessions

Remote sessions can measure idle time and send an extra beat when you come back, if the server allows.

Nothing to try yet In Development
JSON All of v2.1.228
Nothing to try yetTier: how much it should matter to you
1Useful: 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

Idle sampling and reactivation heartbeats are present but do not run unless the server enables them.

What

The remote bridge client can now sample how long a session has been idle and report it in heartbeats, and send an extra "reactivate" heartbeat when activity resumes after an idle period, logged as cli_heartbeat_reactivation_beat. None of it runs in this build unless the server enables it.

Details
Evidence

cli_heartbeat_reactivation_beat

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

Read from
Feature flag
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_ccr_idle_heartbeat 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_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.

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_idle_heartbeat, 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_idle_heartbeat, 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_ccr_reactivation_beat

See this entry in the whole of v2.1.228 →

Feedback