Key points
- Default change date: August 14, 2025; applies to Pro, Max, Team tiers on Claude Code. Enterprise, API, Bedrock, Vertex, and Foundry remain opt-in (to default within ~one month).
- Headline numbers: In a 1,053-user controlled trial, the server-side classifier caught 89% of dangerous commands; manual approval caught 14%, dropping to ~5% after 50 prompts in a session.
- Why the switch is plausible: Users currently approve 97% of permission prompts, ~50% of active CLI users have built broad Bash allow rules (e.g.
python:*), and 62% have usedbypassPermissionsor "don't ask again." - Classifier architecture:
- Input probe scans all server-fetched content (web pages, files, shell output, MCP tool results) for prompt-injection traces and injects warnings back into Claude's context.
- Stage 1: a single-token yes/no filter tuned to over-block.
- Stage 2: chain-of-thought re-review on flagged samples, reducing false positives from 8.5% to 0.4%.
- Structural isolation: the judge sees only the user message and raw tool call — no Claude reasoning and no tool output — so hidden payloads in fetched files cannot influence it.
- Targeted action categories: irreversible ops (deletion, overwrites), destructive ops (with
git-statuscheck beforegit reset --hard), out-of-environment actions (sending code or secrets), and explicit-deny (data exfiltration). After 3 consecutive or 20 cumulative blocks in a session, auto mode falls back to manual approval. - Cost policy: Classifier token usage is excluded from Pro/Max/Team quotas effective immediately — effectively a platform-funded safety tax.
- Field evidence: Across 720 third-party attack scenarios, zero prompt-injection attacks succeeded under auto mode; teams on auto mode shipped 25% more PRs. Adobe, Nuro, Gusto, and Garner Health run auto mode in production.
- Rollback path: Shift+Tab in CLI; mode-switch menu on desktop; admins can pin
defaultModeor setdisableAutoModein managed settings. - Allow-rule interaction: Broad rules like
python:*are temporarily suspended to prevent classifier bypass; other permission rules still run before the classifier. - False-positive cost: 0.4% means ~4 unnecessary blocks per 1,000 tool calls; tolerable for long-running tasks, but users must accept occasional fallback to manual review.
- Anthropic blog: https://claude.com/blog/auto-mode-default-in-claude-code
- Anthropic engineering blog (classifier architecture): https://www.anthropic.com/engineering/claude-code-auto-mode
- @ClaudeDevs X post (08-08 01:27): https://x.com/ClaudeDevs/status/2085794862608318627
- Third-party analysis: https://www.alphasignal.ai/news/anthropic-s-claude-code-auto-mode-catches-dangerous-commands-89-of-the-time
- Chinese coverage (Jiqizhixin / 163): https://www.163.com/dy/article/L3TIBV610511AQHO.html
Why this matters
The change reallocates risk rather than removing it. What was "user fatigue + blanket approval" becomes "classifier interception + occasional false positives." Anthropic still recommends human review for high-stakes changes to production infrastructure. Combined with the same week's cross-session messaging release, the move looks like a paired strategy: more agent autonomy in the harness, paired with a tighter safety net inside the harness.