{"version":"2.1.319","anchor":"permission-decisions-drop-hooksmayrefuse-and-attach-match","canonical_anchor":"permission-decisions-drop-hooksmayrefuse-and-attach-match","heading":"Permission decisions carry less hook detail and can flag a matched ask rule","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/permission-decisions-drop-hooksmayrefuse-and-attach-match","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Permission decisions carry less hook detail and can flag a matched ask rule\n\nA note about hooks is no longer passed along with permission decisions, and a rule check now returns a deny or marks the matching ask rule\n\n**Unclear.** It is not clear how these changes alter which permission prompts you see.\n\n**What**\n\nWhen Claude Code decides whether a tool call needs your permission, it records extra details with the decision. A tool call is an action the model asks to take, such as running a command or editing a file. Two things changed in how those details travel:\n\n- hooksMayRefuse: a note that hooks (your own scripts that run at set points) might refuse the action is no longer copied along with the decision\n\n- ask rules: a step that used to only count a saved outcome now looks up a rule verdict, and returns the deny verdict if there is one, or otherwise the original result marked with the ask rule it matched\n\nAn ask rule is a permission rule that makes Claude Code ask you before doing something.\n\n**Why**\n\nBoth changes are in the code that decides when you see a permission prompt, so they can change when one appears.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}