{"version":"2.1.301","anchor":"subagent-sendresume-budget-between-user-messages","canonical_anchor":"subagent-sendresume-budget-between-user-messages","heading":"Limit on how often agents can be messaged or resumed between your messages","tier":"notice","area":"Subagents","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/subagent-sendresume-budget-between-user-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Limit on how often agents can be messaged or resumed between your messages\n\nMessaging or resuming a subagent now counts against a limit that resets when you write, and is refused with a 'Not sent' message once used up\n\n**Unclear.** It is not clear in which sessions this limit is switched on.\n\n**What**\n\nA subagent is a helper agent that Claude starts to work on part of a task. Sending a subagent a message with `SendMessage`, or resuming one, now counts against a limit between two of your own messages.\n\nWhen that limit is used up, or there is no room left, the request is refused. Claude sees a \"Not sent\" or \"was not resumed\" message saying the session's agents have launched, resumed and written as often as they may before you next write. When a subagent is resumed, the result now also includes a `revivedAgentId` next to `resumedAgentId`.\n\n**Why**\n\nThis stops agents from messaging each other without end. You may see Claude stop and wait for you after a lot of agent activity, until you write again.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}