Claude Code Will Make Auto Mode the Default on August 14

Anthropic is changing the default permission experience in Claude Code. Starting August 14, 2026, new sessions for Pro, Max, and Team users will start in auto mode unless a pinned or administrator-managed default says otherwise. (Claude by Anthropic; ClaudeDevs on X)

Auto mode is not a blanket permission bypass. Claude Code routes each tool call through a separate classifier that evaluates whether the action is irreversible, destructive, or aimed outside the user's environment. When the classifier blocks something, Claude can usually look for a safer path or ask the user to approve the action directly. (Claude by Anthropic)

What changes by plan

If you already pinned a default permission mode, Anthropic says nothing changes. A user who configured a different default may see a one-time prompt, while a Team administrator's managed default takes precedence. Users without a configured default will see an in-product notice as the new behavior arrives. (Claude by Anthropic; ClaudeDevs on X)

How auto mode makes permission decisions

The classifier runs on every tool call. It is intended to catch dangerous actions without forcing the user to review every routine read, edit, or test command. Anthropic says the classifier is designed to block data exfiltration, destructive operations, and actions that move work outside the user's environment. (Claude by Anthropic)

The mode has explicit fallback behavior. Claude Code switches back to manual approvals after three blocks in a row or twenty blocks across a session, according to Anthropic's write-up. Permission rules still run before the classifier, except for broad allow rules that would grant arbitrary code execution, such as python:*; those broad rules are set aside while auto mode is active so they cannot bypass the classifier. (Claude by Anthropic)

Auto mode also screens content returned from external sources for prompt-injection attempts. That safeguard is not a guarantee: Anthropic says the system relies on classification and does not eliminate risk, so high-stakes production changes still deserve direct review. (Claude by Anthropic)

The classifier is no longer charged on three plans

The classifier uses a small number of extra tokens per tool call. As of August 7, 2026, Anthropic says Claude Code users on Pro, Max, and Team plans are no longer charged for that classifier overhead. That is narrower than a promise of higher quotas: the announcement discusses classifier-token treatment, not a general increase to included usage or rate limits. (Claude by Anthropic; ClaudeDevs on X)

Anthropic says it plans to stop charging classifier overhead on Enterprise and the listed API and cloud-platform surfaces when auto mode becomes the default there in the coming month. Enterprise administrators are to be notified before that change. (Claude by Anthropic)

What administrators can control

Organizations do not have to accept one global behavior without controls. Anthropic documents a managed defaultMode setting for pinning the default, and disableAutoMode for turning auto mode off entirely. Administrators can also add hard-deny rules for actions that should never be approved automatically. (Claude by Anthropic)

The announcement describes a few examples of those boundaries: auto mode should deny attempts to send code or secrets to an external destination, inspect the destination of a git push or pull request, and account for the current repository state before a destructive command such as git reset --hard. Those checks are there to preserve context that a simple allowlist cannot see. (Claude by Anthropic)

How to switch back to manual review

In the CLI, press Shift+Tab to change modes. In the desktop app, use the mode dropdown. A pinned personal or managed setting may control the starting state, but Anthropic's documentation still describes mode switching as available to the user. (Claude by Anthropic)

For a cautious rollout, start auto mode on a repository where the test and deployment boundaries are clear. Keep hard-deny rules for production and data-export operations, and inspect the first few long-running sessions rather than treating the new default as an unattended approval to run anything.

What to expect on August 14

The immediate change is behavioral rather than a new model or a new command: a fresh Claude Code session on Pro, Max, or Team will be more willing to continue through routine tool calls without pausing for a prompt. The classifier becomes the review layer, manual mode remains available, and existing pinned or administrator-managed defaults continue to win. (Claude by Anthropic)

The broader implication is that Anthropic is making longer-running Claude Code work the default workflow while keeping a safety boundary around destructive and out-of-environment actions. Teams should update internal guidance before the date, decide which repositories are appropriate for auto mode, and verify that managed settings express the exceptions they care about.

Bottom line

Claude Code auto mode becomes the default for new Pro, Max, and Team sessions on August 14, 2026. It uses a per-tool-call classifier instead of asking for every permission decision, falls back to manual review after repeated blocks, and no longer charges those three plans for classifier overhead. The practical choice for teams is not simply “on or off”: set managed defaults and hard denies for sensitive work, then use auto mode where fewer interruptions are worth the trade-off. (Claude by Anthropic)

Sources

• Claude by Anthropic, “Auto mode is now the default in Claude Code for Pro, Max, and Team plans” (August 7, 2026): https://claude.com/blog/auto-mode-default-in-claude-code
• ClaudeDevs on X, “Starting August 14, auto mode will be the default permission mode in Claude Code” (August 7, 2026): https://x.com/ClaudeDevs/status/2085794862608318627
• ClaudeDevs on X, “Auto mode runs a classifier on every tool call” (August 7, 2026): https://x.com/ClaudeDevs/status/2085794868102889473