Claude Code: Auto Mode Is Now the Default. The Classifier Is Not a Policy.
Anthropic: The human approval habit was the real risk. The data shows it. Auto-mode is now the default.
A lot of drivers think that they’re safer than full self-driving mode. But the data actually show that full self-driving mode is quite a bit safer. You might be surprised that auto mode in Claude Code is actually safer, a lot safer than having a developer approve edits. And if you’ve ever looked at an approve this bash command that’s 8 lines long, full of what looks like line noise, and you’re trying to decipher what it says, you’ll understand why Auto Mode is safer than human approval roulette.
On August 14, 2026, new Claude Code sessions on Pro, Max, and Team start in auto mode. Humans approved 97% of permission prompts. In Anthropic’s own study, humans caught 13.6% of dangerous commands. The classifier caught 89%. The safety load moved. Most teams did not move the harness with it.
Claude Code stops asking today unless you pin a default first.
What Changes on August 14
As of August 14, 2026, Claude Code auto mode is the default for new sessions on the Pro, Max, and Team plans. Anthropic announced the change on August 7.
The product change is small. The engineering change is quieter. The developer who clicked Approve on every Bash call leaves the loop. A classifier takes the seat. The classifier beats a tired reviewer. The classifier is not a policy. If your control says “the developer approves each action”, that control expires today.
This article covers three things. First, what the classifier trusts. Second, which layers still hold after the prompt disappears. Third, what you put in the harness before you leave an agent to run overnight.
Three User States at Rollout
Your experience today depends on what you set before the rollout.
If you never set a default, you get an in-product notice and the new default. If you set a different personal default, you may get a one-time prompt about the switch. If a Team admin pinned a default in managed settings, nothing changes for you.
Which Plans Switch by Default
New sessions on the Pro, Max, and Team plans will start in auto mode on August 14. Classifier overhead is no longer billed on those plans.
Enterprise, the Claude API, Claude Platform on AWS, Amazon Bedrock, Google Cloud’s Agent Platform, and Microsoft Foundry stay opt-in for now. Auto mode is available on all listed platforms. Only the default-mode flip is limited to Pro, Max, and Team. Anthropic plans to flip those remaining defaults in the coming month. Anthropic will notify Enterprise admins first.
How to Leave Auto Mode
You can leave auto mode at any time. Press Shift+Tab in the CLI to cycle through modes. The desktop app and the VS Code and JetBrains extensions use a mode selector.
Admins can pin permissions.defaultMode in managed settings to set a default for the org. Admins can also remove auto mode entirely from the rotation. Set permissions.disableAutoMode to the string "disable" in managed settings. This removes auto from the Shift+Tab cycle and rejects --permission-mode auto at startup.
Why the Repo Settings File Cannot Grant Auto Mode
permissions.defaultMode: "auto" is honored in ~/.claude/settings.json and in managed settings. Claude Code v2.1.142 and later ignore the auto value from .claude/settings.json and .claude/settings.local.json. The user settings file and managed settings still honor it.
The behavior is deliberate. A cloned repository cannot grant itself auto mode.
The policy and the configuration options are now clear. The evidence behind them comes next. Anthropic did not flip the default on a theoretical argument about classifier ability. Anthropic flipped it on measured data about how human reviewers behaved. The data covers approval rates, decay over the length of a session, and a controlled study.
The Evidence: The Classifier Beat the Permission Prompt
If you are a paid subscriber, thank you. Your support makes this work possible.
If you are a free subscriber and find these articles useful, please consider upgrading. A paid subscription is $80 per year or $8 per month.
