{"version":"2.1.281","anchor":"you-can-no-longer-save-always-allow-rules-from-non-classifie","canonical_anchor":"you-can-no-longer-save-always-allow-rules-from-non-classifie","heading":"You can no longer save always-allow rules from non-classifier-approvable safety-check prompts","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/you-can-no-longer-save-always-allow-rules-from-non-classifie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### You can no longer save always-allow rules from non-classifier-approvable safety-check prompts\n\nChoosing \"always allow\" on a prompt raised by a safety check the classifier cannot approve no longer saves a rule\n\n**What**\n\nWhen Claude Code asks your permission before doing something, you can usually choose to always allow it, which saves a rule so you are not asked again. For prompts caused by a safety check that is marked as not approvable by the automatic classifier (`classifierApprovable` false), that saved rule is now dropped. You can still allow the action once, but no \"always allow\" rule is kept.\n\n**Why**\n\nThese prompts will keep appearing each time the same safety check is triggered, so every such action gets your explicit approval.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}