{"version":"2.1.281","anchor":"keepalive-after-stop-flag-check-refactored-to-take-the-flag","canonical_anchor":"keepalive-after-stop-flag-check-refactored-to-take-the-flag","heading":"Keepalive-after-stop flag check refactored to take the flag name","tier":"internal","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/keepalive-after-stop-flag-check-refactored-to-take-the-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Keepalive-after-stop flag check refactored to take the flag name\n\nThe keepalive-after-stop check was restructured to take its flag name as a parameter, with no change in behaviour\n\n**What**\n\nThe 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.\n\nAt 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.\n\n**Why**\n\nThe 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.\n\n- Flag `tengu_ccr_keepalive_after_stop_enabled`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.281; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}