{"version":"2.1.321","anchor":"auto-mode-classifier-unavailable-now-blocks-agent-start-with","canonical_anchor":"auto-mode-classifier-unavailable-now-blocks-agent-start-with","heading":"Auto mode refuses to start a subagent when its safety check is unavailable","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/auto-mode-classifier-unavailable-now-blocks-agent-start-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Auto mode refuses to start a subagent when its safety check is unavailable\n\nIn auto mode, a subagent is not started if the safety classifier cannot check its prompt, and Claude Code says why\n\n**What**\n\nIn auto mode, Claude Code uses a classifier (a model that reviews actions) to decide whether something is safe to do without asking you. A subagent is a helper agent Claude starts to work on part of a task.\n\nWhen the classifier cannot check a subagent's prompt, the subagent is now not started. The reason given says the conversation may be too long, or to try again in a few minutes.\n\nThe warning shown when a subagent's output is passed on without review has new wording. Which warning appears now depends on the environment variable `CLAUDE_CODE_USER_DELEGATED_SESSION_DIRECT_API`.\n\n**Why**\n\nIn auto mode, starting a subagent can now fail when the classifier is down, so you may need to retry.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}