{"version":"2.1.319","anchor":"always-allow-rule-suppression-logic-dropped-from-permission","canonical_anchor":"always-allow-rule-suppression-logic-dropped-from-permission","heading":"Change to when permission prompts offer an always-allow option","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/always-allow-rule-suppression-logic-dropped-from-permission","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Change to when permission prompts offer an always-allow option\n\nPermission prompts now use a precomputed choice about hiding the always-allow option, and asks reserved for a person now always count\n\n**Unclear.** It is not clear whether the always-allow option now appears more often, less often, or in the same cases as before.\n\n**What**\n\nA permission prompt is the question Claude Code asks before running an action, and it can offer an option to always allow that action from now on. Claude Code no longer works out at the prompt whether to hide that option; it uses a value decided earlier.\n\nSeparately, a rule that says an action must be approved by a person now always counts, even when the automatic safety checker might have allowed it.\n\n**Why**\n\nThe always-allow option may appear in different cases than before, and actions marked as needing a person's approval are no longer waved through by the checker.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}