{"version":"2.1.323","anchor":"permission-ask-results-from-in-place-checks-preserved-over-r","canonical_anchor":"permission-ask-results-from-in-place-checks-preserved-over-r","heading":"Permission prompts that need a person are no longer replaced by rule prompts","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/permission-ask-results-from-in-place-checks-preserved-over-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Permission prompts that need a person are no longer replaced by rule prompts\n\nWhen a tool says a person must approve, that prompt now wins over a general rule prompt, and a crashed check now denies\n\n**What**\n\nBefore a tool runs, Claude Code checks your permission rules and the tool's own checks. Some tools say a person must approve the action. That request now takes the place of the general prompt from your rules, unless the rule prompt already covers it.\n\nA note that a check did not finish is now carried over too. If the tool's own check crashes, the result is now a denial.\n\n**Why**\n\nBefore, the rule prompt always replaced the tool's own result. Prompts that need a person can no longer be swapped for a more general one.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}