{"version":"2.1.265","anchor":"nested-blocked-agent-chains-now-release-a-park-callback-on-u","canonical_anchor":"nested-blocked-agent-chains-now-release-a-park-callback-on-u","heading":"Nested blocked agent chains now release a park callback on unblock","tier":"internal","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/nested-blocked-agent-chains-now-release-a-park-callback-on-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Nested blocked agent chains now release a park callback on unblock\n\nNested blocked agent chains now properly release their pending callback when unblocked\n\n**What**\n\nWhen a chain of blocked, nested agents (agents waiting on each other) gets unblocked, Claude Code now runs a stored callback for that chain via a new `releaseNestedChainPark` mechanism, then clears the stored callback (`nestedChainUnparks`) so it isn't run again.\n\n**Why**\n\nThis is internal plumbing for how nested agent chains resume after being blocked. It reduces the chance of a leftover callback firing incorrectly or a chain failing to fully resume.\n\n- Area: Background Agents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}