A subagent can now report itself as blocked instead of claiming it succeeded or failed.
What's wrong with this entry?
The 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.
- The change is in the instructions given to the model, in the notification format it fills in for finished tasks.
- Applies to any session that receives this system prompt section; there is no setting to turn it on or off.
<status>completed|failed|killed|blocked</status>
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Another forged control tag is escaped in subagent output
Both mention subagent
-
v2.1.234
Spawned processes get
--flag=valuewhen the value looks like a flagBoth mention subagent
-
v2.1.235
New error for delegating to a subagent without naming one
Both mention subagent