{"version":"2.1.314","anchor":"subagent-wake-failures-can-be-handed-to-the-main-agent","canonical_anchor":"subagent-wake-failures-can-be-handed-to-the-main-agent","heading":"Background helper agent notifications go to the main agent instead of being dropped","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/subagent-wake-failures-can-be-handed-to-the-main-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Background helper agent notifications go to the main agent instead of being dropped\n\nIf a helper agent fails to wake up, its waiting notifications now go to the main agent rather than being thrown away\n\n**What**\n\nA subagent is a helper agent that Claude starts to work on part of a task, sometimes in the background. Such an agent can have task notifications waiting for it, which are messages about work that has finished.\n\nBefore, if the helper agent failed to wake up because of a resume error, those notifications were dropped. Now, as long as you did not stop the agent yourself, they are handed to the main agent instead.\n\nWhen a recorded helper agent is resumed, Claude Code also keeps track of a question it was waiting on. If the resume never happens, that question is closed and marked as \"not_resumed\".\n\n**Why**\n\nUpdates from background agents are less likely to be lost without any sign, so the main agent can still act on them.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}