Resuming or forking a subagent that fails now gives a clear tool error instead of a raw crash.
What's wrong with this entry?
An exception while rebuilding a resumed subagent's system prompt used to escape raw; it is now caught and surfaced as a tool error.
- Failures are reported with a dedicated failure code.
- The error is rethrown as the tool's own error type rather than the original exception.
subagent_resume_fork_prompt_reconstruct_failed
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