{"version":"2.1.293","anchor":"orphaned-background-agent-resume-messages-depend-on-whether","canonical_anchor":"orphaned-background-agent-resume-messages-depend-on-whether","heading":"Claude no longer told to message background agents it cannot continue","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/orphaned-background-agent-resume-messages-depend-on-whether","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Claude no longer told to message background agents it cannot continue\n\nWhen a background agent cannot be continued, Claude is now told to relaunch it or check its output instead of sending it a message\n\n**What**\n\nA background agent is a helper Claude starts to work on part of a task while it carries on. When a session is restored and such an agent was left stopped, Claude used to always be told to resume it by sending it a message with `SendMessage`. Now that depends on whether the agent can actually be continued:\n\n- If it can, Claude is told to send it a message as before.\n\n- If it cannot, Claude is told to launch it again or check its output. Claude is also told not to assume the task got done, and to launch it again if the result is still needed.\n\nWhen continuing is not possible, Claude is also told that \"A previously spawned agent cannot be continued from here\". Stopped agents are now listed in separate notices depending on whether they can be continued and whether their output can be read.\n\n**Why**\n\nClaude no longer tries to message agents that cannot answer, which would waste a step or leave work silently undone.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}