{"version":"2.1.265","anchor":"hook-events-pretooluse-split-into-classic-vs-new-and-two","canonical_anchor":"hook-events-pretooluse-split-into-classic-vs-new-and-two","heading":"Hook events: PreToolUse split into classic vs. new, and two new synchronous hook events added","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/hook-events-pretooluse-split-into-classic-vs-new-and-two","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Hook events: PreToolUse split into classic vs. new, and two new synchronous hook events added\n\nPreToolUse hooks are now split into a classic and new form, plus two new synchronous hook events\n\n**Unclear.** What distinguishes the new 'classic.PreToolUse' from a non-classic PreToolUse, and what command.run\/command.describe hooks are used for, is not explained in the finding.\n\n**What**\n\nThe logic that warns when a hook blocks a turn now specifically matches `classic.PreToolUse` rather than a plain `PreToolUse` event, implying `PreToolUse` (a hook that runs before a tool call executes and can block it) now has both a classic and a newer variant. Two new events, `command.run` and `command.describe`, have also been added to the set of hook events where submitting mid-hook will wait on the current turn to finish.\n\n**Why**\n\nThis affects how hooks interact with turn timing: hooks tied to `command.run` and `command.describe` now behave like other turn-blocking hook events, so anything relying on those events should account for that wait.\n\n- Area: Hooks\n- Names: `classic.PreToolUse`, `command.run`, `command.describe`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}