You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.295,
ImprovementsSection of the release
Unclear It is not clear whether this step decides if a tool call is blocked or only records the decision, so it is unknown whether a deny from a hook still stops the call.
What
Hooks are your own scripts that Claude Code runs at set moments, such as before a tool call (an action Claude takes, like running a command or editing a file). Claude Code has a step that turns a hook's answer into a permission decision. That step has changed:
PermissionRequest hook: the answer is now always read as "allow". Before, the step used the decision the hook returned.
PreToolUse hook: the hook's permission decision is used only when it is set and is not "deny". Before, any decision was used.
Why
A hook that answers "deny" is now handled differently by this step. If you rely on hooks to refuse tool calls, check that they still do what you expect.
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 doubtIt is not clear whether this step decides if a tool call is blocked or only records the decision, so it is unknown whether a deny from a…
