{"version":"2.1.321","anchor":"stopped-background-tasks-notify-a-target-agent","canonical_anchor":"stopped-background-tasks-notify-a-target-agent","heading":"Notices about stopped background tasks can now go to another agent","tier":"internal","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/stopped-background-tasks-notify-a-target-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Notices about stopped background tasks can now go to another agent\n\nWhen a background task is stopped, its notice can now carry a message and go to a chosen agent, which is told right away\n\n**Unclear.** It is not clear what, if anything, you see differently when a background task is stopped.\n\n**What**\n\nA background task is work Claude Code keeps running while you carry on. When one is stopped, Claude Code sends a notice about it. Before, that notice always went to the current agent, an agent being one running copy of Claude working on a task. It was delivered quietly. The notice can now carry a message and be sent to a different agent. When it goes to another agent, it is delivered actively instead of quietly.\n\n**Why**\n\nThis changes how stop notices reach subagents, which are helper agents Claude Code starts for part of a job.\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}