Stopping one agent still stops them all, though the code to spare some is now present.
Each agent is tested against an exemption rule list before being killed, but nothing ever adds a rule, so none are spared.
What's wrong with this entry?
Stopping an agent still stops every other running agent with it. New in this build is the machinery to exempt some of them: each other agent is tested against a list of exemption rules and, if exempt, added to a "spared" list instead of being killed. Nothing in this build ever adds a rule to that list, so no agent is ever spared and stops cascade exactly as before.
- The exemption list lives on the shared registry of running agent tasks; the bundle contains its declaration and one place that reads it, and nothing that writes to it.
- The spared list is announced through a
cascadeSparedevent that nothing in the build listens for. - There is no flag or setting; the feature is inert because the rule list is empty.
cascadeStopExemptions
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