{"version":"2.1.321","anchor":"sendmessage-to-stopped-agents-distinguishes-stopped-by-user","canonical_anchor":"sendmessage-to-stopped-agents-distinguishes-stopped-by-user","heading":"Messages to a stopped agent now say whether you stopped it","tier":"notice","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/sendmessage-to-stopped-agents-distinguishes-stopped-by-user","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Messages to a stopped agent now say whether you stopped it\n\nSending to a stopped helper agent now says it was stopped by the user only when it was, and simply \"was stopped\" otherwise\n\n**What**\n\nClaude can start helper agents and send them messages with the `SendMessage` tool. When a message goes to an agent that has stopped and is not resumed, the reply now depends on why it stopped:\n\n- if you stopped it, it says the agent \"was stopped by the user\"\n\n- otherwise, it says the agent \"was stopped\"\n\nBoth go on to say the agent was not resumed and that its work should be treated as cancelled. Before, the reply always said the agent was stopped by the user. When an agent is resumed, it now also keeps the critical reminders it inherited.\n\n**Why**\n\nThe wording is now accurate when an agent stopped for a reason other than you.\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}