Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

New keepalive frames after Stop for remote (CCR) sessions, gated off by default

Remote (CCR) sessions gain keepalive messages after a turn stops, currently off by default

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

For remote sessions (using Claude Code Remote, referred to internally as CCR), Claude Code now has a mechanism that sends periodic "keepalive" messages after a turn stops, as long as background tasks are still running (up to a limit). This only applies when the CLAUDE_CODE_REMOTE environment variable is set, and is controlled by a setting called tengu_ccr_keepalive_after_stop_enabled. When a keepalive session ends, it logs an event recording why it stopped, how many keepalive messages were sent, and how long it was active.

Why

Keepalive messages help keep a remote connection alive while background work continues after you've stopped a turn. The setting controlling this, tengu_ccr_keepalive_after_stop_enabled, was found off both for this site's account and for the general baseline, and no reading has been taken yet under this release.

Read from
Feature flag
tengu_ccr_keepalive_after_stop_enabled Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.277: 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.277. It isn't a statement about your account. What a flag value here can and cannot tell you

What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Monitoring. By default, metrics and events from a cloud session carry the [standard attributes](#standard-attributes), including `session.id`, `ccr.session.id`, and `organization.id`, so you can filter by session or organization without extra configur… monitoring-usage see the edit
What has happened since
Flag reading moved The flag server now returns on for tengu_ccr_keepalive_after_stop_enabled, 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
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Monitoring.
The name it cites is new in this buildNew in this build: tengu_ccr_keepalive_after_stop_enabled

See this entry in the whole of v2.1.277 →

Feedback