Remote (CCR) sessions gain keepalive messages after a turn stops, currently off by default
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.
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.
tengu_ccr_keepalive_after_stop_enabled Off in both readingsThe 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
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_keepalive_after_stop_enabled