{"version":"2.1.239","anchor":"nested-agent-activity-is-tracked-per-chain-with-eviction","canonical_anchor":"nested-agent-activity-is-tracked-per-chain-with-eviction","heading":"Nested agent activity is tracked per chain with eviction","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/nested-agent-activity-is-tracked-per-chain-with-eviction","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Nested agent activity is tracked per chain with eviction\n\nNested agent chains now track their activity separately instead of sharing one global state.\n\n**What**\n\nActivity 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.\n\n**Details**\n\n- Listeners were split into one for the main loop and one for dropped nested chains.\n\n**Evidence**\n\n`nestedChainDropListener`\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}