{"version":"2.1.267","anchor":"auto-mode-safety-classifier-now-explicitly-blocks-when-its","canonical_anchor":"auto-mode-safety-classifier-now-explicitly-blocks-when-its","heading":"Auto-mode safety classifier now explicitly blocks when it's unavailable or the transcript is too long, but only for large output schemas","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/auto-mode-safety-classifier-now-explicitly-blocks-when-its","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Auto-mode safety classifier now explicitly blocks when it's unavailable or the transcript is too long, but only for large output schemas\n\nAuto mode now explicitly blocks large tool outputs when its safety classifier can't run\n\n**What**\n\nWhen Claude Code runs in auto mode (which can act on tool results without asking first), it uses a classifier to help decide whether output is safe to proceed with. That decision logic now has a new \"blocked\" outcome, separate from the existing \"unavailable,\" \"refused,\" and \"allowed\" outcomes. It triggers when the classifier is unavailable or the conversation transcript is too long to classify, but only when the tool's output schema is large. The reason given is either \"classifier context exceeded; output schema too large to pass unreviewed\" or \"classifier unavailable; output schema too large to pass unreviewed,\" and the result now also includes an `unreviewed` true\/false flag.\n\n**Why**\n\nThis closes a gap where a large, unreviewable tool output could otherwise slip through auto mode simply because the safety classifier couldn't run; now it's explicitly blocked instead.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}