{"version":"2.1.301","anchor":"auto-mode-classifier-denial-now-records-the-decision-reason","canonical_anchor":"auto-mode-classifier-denial-now-records-the-decision-reason","heading":"Automatic denials from safety checks now record why they were denied","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/auto-mode-classifier-denial-now-records-the-decision-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Automatic denials from safety checks now record why they were denied\n\nWhen Claude Code automatically turns down a risky action, the record of that decision now includes the reason for the denial\n\n**What**\n\nA safety check is a point where Claude Code stops before doing something risky. When one of these checks is denied automatically, without anyone being asked, Claude Code writes down the decision. That record used to hold only two things: that the action was rejected, and that the rejection came from configuration. It now also holds the reason for the decision.\n\n**Why**\n\nThe permission records and usage reports now say why a request was refused, not only that it was refused.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}