{"version":"2.1.293","anchor":"hook-runner-can-wait-on-a-gate-and-tracks-hooks-that-ran-els","canonical_anchor":"hook-runner-can-wait-on-a-gate-and-tracks-hooks-that-ran-els","heading":"Hooks can now wait on a check before they run","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/hook-runner-can-wait-on-a-gate-and-tracks-hooks-that-ran-els","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Hooks can now wait on a check before they run\n\nClaude Code can now hold hooks until a pre-check finishes, and can mark a hook's result as having already run somewhere else\n\n**Unclear.** It is not clear what the hooks now wait for or which sessions this affects.\n\n**What**\n\nHooks are your own commands that Claude Code runs automatically at set moments, such as before a tool runs. Claude Code can now wait for a check to finish before it runs your hook handlers, and then carries on. A hook result can also be marked as having already run somewhere else, and Claude Code adjusts the hook's input when that happens.\n\n**Why**\n\nThis changes the order in which hooks run and how some of their results are handled.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}