{"version":"2.1.275","anchor":"orphaned-backgrounded-tasks-get-auto-aborted-and-quietly-par","canonical_anchor":"orphaned-backgrounded-tasks-get-auto-aborted-and-quietly-par","heading":"Orphaned backgrounded tasks get auto-aborted and quietly parked","tier":"soon","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/orphaned-backgrounded-tasks-get-auto-aborted-and-quietly-par","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Orphaned backgrounded tasks get auto-aborted and quietly parked\n\nBackground tasks left running after their owning agent disappears are now automatically stopped\n\n**What**\n\nWhen a task running in the background loses its owning agent (the agent that started it no longer exists), Claude Code now detects this and automatically stops it, rather than letting it keep running indefinitely. This only happens for tasks that are actually running in the background, have a way to be cancelled, and have already produced at least one successful (non-error) response. Once stopped this way, the task is marked as notified and \"quietly parked.\"\n\nA related change also adjusts how the app decides whether a completed background task still needs to stay alive, based on whether it's backgrounded and not already in another state.\n\n**Why**\n\nThis prevents orphaned background tasks from consuming resources or running forever after the thing that started them is gone, while still preserving whatever useful output they had already produced.\n\n- Flag `tengu_zinc_harbor`: Off in both readings (read for one account on one subscription tier against v2.1.275; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Background Tasks\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}