{"version":"2.1.323","anchor":"hook-ask-floor-debug-message-reworded","canonical_anchor":"hook-ask-floor-debug-message-reworded","heading":"Debug log reworded for when a PreToolUse hook cannot settle permissions","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/hook-ask-floor-debug-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Debug log reworded for when a PreToolUse hook cannot settle permissions\n\nThe debug message for a PreToolUse hook that cannot settle a permission now says the rule check objected or could not run\n\n**Unclear.** Whether the permission behaviour itself changed, or only the wording of the log message.\n\n**What**\n\nA `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.\n\nThe 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.\n\n**Why**\n\nThe new wording suggests the full permission checks now also take over when the rule check fails to run, not only when it objects.\n\n- Area: Hooks\n- Names: `PreToolUse`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}