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.265,
Internal ChangesSection of the release
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.
What
The 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.
Why
This 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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up command.run, on Troubleshoot a mod.### `no command.run hook answered it`plugins/mods/troubleshootsee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat distinguishes the new 'classic.PreToolUse' from a non-classic PreToolUse, and what command.run/command.describe hooks are used for, is…
Anthropic's documentation agreesAnthropic's documentation has since written up command.run, on Troubleshoot a mod.
