{"version":"2.1.315","anchor":"task-notifications-can-be-passive-session-copy-flag-passed","canonical_anchor":"task-notifications-can-be-passive-session-copy-flag-passed","heading":"Task notifications can now be marked passive","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/task-notifications-can-be-passive-session-copy-flag-passed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Task notifications can now be marked passive\n\nMessages queued when a background task reports back can now be marked passive, and sessions now pass on whether they began as a copy\n\n**What**\n\nWhen a background task reports back, Claude Code queues a task notification message for Claude. That message can now be marked as passive. Separately, a session's options now pass along a flag recording whether the session began as a copy of another one.\n\n**Why**\n\nThe passive mark gives Claude Code a way to treat some task notifications differently from the rest.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}