{"version":"2.1.268","anchor":"blocked-content-refusal-reason-can-now-surface-a-specific-po","canonical_anchor":"blocked-content-refusal-reason-can-now-surface-a-specific-po","heading":"Blocked-content refusal reason can now surface a specific policy category","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/blocked-content-refusal-reason-can-now-surface-a-specific-po","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Blocked-content refusal reason can now surface a specific policy category\n\nBlocked-content refusal messages can now name the specific policy category that triggered them\n\n**What**\n\nWhen Claude Code's fast safety classifier blocks some content, it now tries to pull a `<category>` tag out of the classifier's raw response. If that category matches one of a known set, the refusal message now shows a bracketed category name (like `[category name]`) instead of always showing the same generic fallback message.\n\n**Why**\n\nThis gives a more specific explanation of why content was blocked, when the classifier's response identifies a known category, instead of a one-size-fits-all message.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}