Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
What
When 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.
Why
This 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.
