{"version":"2.1.301","anchor":"background-shells-marked-elsewhere-no-longer-count-as-an-a","canonical_anchor":"background-shells-marked-elsewhere-no-longer-count-as-an-a","heading":"Background shells running elsewhere no longer count as an agent's live work","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-shells-marked-elsewhere-no-longer-count-as-an-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Background shells running elsewhere no longer count as an agent's live work\n\nA background shell marked as running elsewhere no longer counts when Claude Code checks whether an agent still has background work running\n\n**What**\n\nClaude Code checks whether an agent still has work running in the background, such as a shell command left running or a connection being monitored. Background shell commands marked as running elsewhere are now left out of that check.\n\n**Why**\n\nThis can change when a session counts as still having background work in progress.\n\n- Area: Background Shells\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}