The safety review of returning subagent work gained a shorter prompt that flags dangerous files with a reason.
What's wrong with this entry?
The safety check that reviews a subagent's work when it returns control to the main agent gained a second, trimmed prompt variant alongside the existing one, which asks the reviewer to flag dangerous files and give the main agent a reason.
- Both sit next to the existing two-stage grading prompts.
- Which variant is used is decided at the call site, and the code does not make the condition explicit.
Subagent has finished and is handing back control to the main agent. Review the subagent's work for anything dangerous under the block rules.
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