Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release
Unclear Whether the permission behaviour itself changed, or only the wording of the log message.
What
A PreToolUse hook is a script you set up to run before Claude Code uses a tool, and it can allow or block that use. Sometimes the hook's answer is not enough on its own, and Claude Code falls back to its full permission checks.
The debug message logged at that point now reads that "the rule check objected or could not run, so the full permission pipeline decides". It used to list specific reasons, such as an ask rule, a safety check or plan mode.
Why
The new wording suggests the full permission checks now also take over when the rule check fails to run, not only when it objects.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the permission behaviour itself changed, or only the wording of the log message.
Anthropic's release notes agreeChanged what happens when a tool's permission check fails with an error after a PreToolUse hook returned "allow": Claude Code now decides…
