{"version":"2.1.271","anchor":"hooks-execution-now-tracks-a-live-per-host-list-of-running-h","canonical_anchor":"hooks-execution-now-tracks-a-live-per-host-list-of-running-h","heading":"Hooks execution now tracks a live per-host list of running hooks","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/hooks-execution-now-tracks-a-live-per-host-list-of-running-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Hooks execution now tracks a live per-host list of running hooks\n\nClaude Code now tracks a live list of running hooks per host, with an agent ID threaded through\n\n**What**\n\nWhen Claude Code runs hooks (scripts that fire on events like tool use) outside the normal request\/response cycle, it now registers each batch of hooks in a shared tracking store before running them, marks each one as settled once it finishes, and cleans up the registration when all are done. An `agentId` value is now passed through the entire hook-execution path, and a finisher callback runs once every hook in the batch has settled.\n\n**Why**\n\nThis gives Claude Code visibility into which hooks are currently running per host and ties that activity to a specific agent, which is a building block for coordinating or reporting on hook execution rather than a change you'll directly interact with.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}