{"version":"2.1.273","anchor":"taskagent-liveness-check-gains-new-exclusions","canonical_anchor":"taskagent-liveness-check-gains-new-exclusions","heading":"Task\/agent liveness check gains new exclusions","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/taskagent-liveness-check-gains-new-exclusions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Task\/agent liveness check gains new exclusions\n\nClaude Code's check for whether a running task counts as 'live' now excludes more cases, including certain in-process teammate tasks\n\n**What**\n\nClaude Code has an internal function that decides whether a running or pending task should still be treated as 'live' (active). It now also treats a task as not-live when a new condition is true, and specifically for tasks of type `in_process_teammate` where `evictAfter` is `0`, there's no `currentWorkAbortController`, and another new condition holds.\n\nThe handling of the 'ambient'\/`monitor_ws` case was also simplified to always report not-live, instead of delegating that decision elsewhere.\n\n**Why**\n\nThis tightens up which tasks Claude Code considers still active, which affects things like whether a task shows as running or gets treated as finished\/evicted.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}