{"version":"2.1.302","anchor":"async-hook-delivery-no-longer-removes-hooks-from-the-registr","canonical_anchor":"async-hook-delivery-no-longer-removes-hooks-from-the-registr","heading":"Async hooks are no longer removed from the list after they deliver results","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/async-hook-delivery-no-longer-removes-hooks-from-the-registr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Async hooks are no longer removed from the list after they deliver results\n\nClaude Code no longer removes hooks that run in the background from its list once their results have been collected\n\n**Unclear.** It is not clear whether finished background hooks are now cleaned up elsewhere or simply stay registered.\n\n**What**\n\nHooks are your own commands that Claude Code runs at set points. Some run asynchronously, meaning in the background while Claude Code carries on. Claude Code used to remove such hooks from its list once it had collected their results. That removal step is gone. How these hooks are registered was also reworked.\n\n**Why**\n\nBackground hooks may now stay registered after they finish, or be cleaned up somewhere else.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}