You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.309,
ImprovementsSection of the release
Unclear What Claude Code does differently with a hook-requested prompt is not stated.
What
A hook is a script you configure to run at set points, for example before a tool is used. A hook can answer that the user should be asked before the tool runs. Claude Code now passes this to its permission check as hookAsked: true when the hook's decision was "ask", next to the existing planModeWriteFloor.
The check that uses a hook's updated tool input now also requires that the hook did not ask.
The exception is a tool that needs user interaction anyway.
When a hook asked, the tool is no longer allowed automatically just because the hook supplied new input.
Why
If your PreToolUse hooks return "ask" together with changed input, expect to be prompted rather than having the tool go ahead on its own.
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 Claude Code does differently with a hook-requested prompt is not stated.
