Nested agent chains now track their activity separately instead of sharing one global state.
What's wrong with this entry?
Activity tracking for nested agents moved from a single module-level map into a class that keys state by chain, evicts old keys under a cap and cleans up that key's heartbeat and idle timers. Nothing changes on screen, but concurrent agent chains are now accounted for separately instead of sharing one global state.
- Listeners were split into one for the main loop and one for dropped nested chains.
nestedChainDropListener
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