{"version":"2.1.305","anchor":"auto-mode-classifier-refusal-no-longer-gated","canonical_anchor":"auto-mode-classifier-refusal-no-longer-gated","heading":"Auto mode now always blocks when the safety check refuses","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/auto-mode-classifier-refusal-no-longer-gated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Auto mode now always blocks when the safety check refuses\n\nWhen the auto mode safety check is unavailable because it refused, Claude Code now always blocks with `policy_refusal`, with no extra condition\n\n**What**\n\nIn auto mode, a check on the server decides whether an action is safe to run. When that check is unavailable because it refused, Claude Code can block the action with a `policy_refusal` result.\n\nThat blocking no longer depends on an extra feature check. A refusal now always produces the `policy_refusal` block.\n\n**Why**\n\nA safeguard that used to apply only in some cases now applies every time, so a refused check always stops the action rather than sometimes falling through to other handling.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}