{"version":"2.1.239","anchor":"subagents-can-report-that-they-are-blocked","canonical_anchor":"subagents-can-report-that-they-are-blocked","heading":"Subagents can report that they are blocked","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/subagents-can-report-that-they-are-blocked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Subagents can report that they are blocked\n\nA subagent can now report itself as blocked instead of claiming it succeeded or failed.\n\n**What**\n\nThe status a subagent reports back to the session that launched it now includes `blocked`, alongside `completed`, `failed` and `killed`, so a task that is stuck waiting on something can say so instead of being forced to claim success or failure.\n\n**Details**\n\n- The change is in the instructions given to the model, in the notification format it fills in for finished tasks.\n- Applies to any session that receives this system prompt section; there is no setting to turn it on or off.\n\n**Evidence**\n\n`<status>completed|failed|killed|blocked<\/status>`\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}