{"version":"2.1.280","anchor":"new-error-classification-for-api-policy-blocked-safety-res","canonical_anchor":"new-error-classification-for-api-policy-blocked-safety-res","heading":"New error classification for API 'policy_blocked' safety responses","tier":"internal","area":"Error Handling","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-error-classification-for-api-policy-blocked-safety-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New error classification for API 'policy_blocked' safety responses\n\nClaude Code now recognizes a distinct API error for safety-policy-blocked requests\n\n**What**\n\nClaude Code can now detect a specific kind of API error: an HTTP 400 response whose body reports `error.type === 'policy_blocked'`. This is now classified separately using a new constant, `safety_monitor_blocked`.\n\n**Why**\n\nThis lets Claude Code tell a safety-policy block apart from other generic 400 errors, which should make it possible to handle or explain this case more precisely instead of treating it like any other bad request.\n\n- Area: Error Handling\n- Names: `safety_monitor_blocked`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}