{"version":"2.1.319","anchor":"background-workers-on-a-gateway-whose-build-was-deleted-are","canonical_anchor":"background-workers-on-a-gateway-whose-build-was-deleted-are","heading":"Background sessions on a gateway are kept when their build is deleted","tier":"notice","area":"Sessions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/background-workers-on-a-gateway-whose-build-was-deleted-are","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Background sessions on a gateway are kept when their build is deleted\n\nClaude Code's cleanup no longer retires background workers held on their gateway just because their Claude Code build was deleted\n\n**What**\n\nClaude Code can run background workers, sessions that keep going without a terminal open, and it regularly clears out ones that have finished. Before, that cleanup retired finished workers by its normal rules. Now a worker held on its gateway is kept even when the Claude Code build it runs on has been deleted. The log records the reason as kept on its gateway because its build was deleted.\n\n**Why**\n\nBackground sessions on a gateway are not lost when an upgrade removes the build they were started with.\n\n- Flag `tengu_bg_prewarm_per_sweep`: Not enough to say (read for one account on one subscription tier against v2.1.319; this account: no value returned, anonymous baseline: no value returned, 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: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}