Subagents now announce when they finish, fail or are killed, and nothing listens yet.
Settled, spawned and resume-failed subagent events are published with no subscriber in this build.
What's wrong with this entry?
Subagent completion, failure and kill now publish a settled event carrying the outcome ("completed" with a stranded-messages flag, "failed", or "killed"). Nothing in this build subscribes to it, nor to the spawned and resume-failed events; the only subagent channel with a listener is the stranded-messages one. This is groundwork with no visible effect yet.
agentSettled
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