The code that picks the keepalive-after-stop mode (off, on or cold) now receives its flag name as an input. The only name passed in is tengu_ccr_keepalive_after_stop_enabled, and its fallback is still false. Behaviour is unchanged.
At the most recent reading, which was not taken under this release, the flag server returned on for tengu_ccr_keepalive_after_stop_enabled for this site's account and for the anonymous baseline. It had switched on since the reading before. That flag was first seen on 2026-09-21.
The restructuring itself changes nothing you will notice. The flag reading shows the server now answers on for this gate, even though the code's own fallback is false.
tengu_ccr_keepalive_after_stop_enabled On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.281: not a boolean we can read
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.281. It isn't a statement about your account. What a flag value here can and cannot tell you