{"version":"2.1.299","anchor":"permission-check-failure-message-now-mentions-hooks","canonical_anchor":"permission-check-failure-message-now-mentions-hooks","heading":"Refusal message for unchecked settings now mentions hooks","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/permission-check-failure-message-now-mentions-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Refusal message for unchecked settings now mentions hooks\n\nWhen settings cannot be checked for an action, the refusal now says \"the rules and hooks in your settings\" could not be checked\n\n**What**\n\nIf Claude Code cannot check your settings for an action Claude wants to take, it refuses the action to stay safe. The message now reads \"the rules and hooks in your settings could not be checked for this call, so it is refused\". Before, it mentioned only the deny rules. Hooks are your own commands that Claude Code runs at set points.\n\n**Why**\n\nThe wording you see when an action is refused this way is different, and it now points at hooks as well as rules.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}