{"version":"2.1.284","anchor":"task-notification-schema-gains-an-internal-producer-sessio","canonical_anchor":"task-notification-schema-gains-an-internal-producer-sessio","heading":"Task notifications can mark work the session started itself","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/task-notification-schema-gains-an-internal-producer-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Task notifications can mark work the session started itself\n\nTask notifications about work the session launched itself, like background agents or shells, can now be labelled as such\n\n**Unclear.** What sets the label is not known.\n\n**What**\n\nClaude Code sends notifications to the conversation when a task finishes or changes. Those reporting on work the session itself launched, such as background agents, shells, workflows or monitors, can now carry an internal label saying so. Notifications from webhooks and artifacts do not carry it.\n\n**Why**\n\nClaude Code can tell follow-ups about its own work apart from events coming from outside.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}