Replayed subagent messages no longer kick off a new top-level turn.
What's wrong with this entry?
Messages arriving on the REPL bridge that belong to a subagent are now dropped on arrival instead of being processed as if you had typed them, which prevents replayed subagent activity from starting a new top-level turn.
Ignoring parented user frame at ingress (echo/replay of a subagent frame)
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