Claude Code's Auto Mode Becomes the Default on August 14
Claude Code's auto mode becomes the default setting for new sessions on Pro, Max, and Team plans starting August 14, 2026.
What it is
An update to Claude Code's auto mode, a setting that governs how much autonomy the agent gets during a session, moving from opt-in to on-by-default for most plans.
What it does
Starting August 14th, new Claude Code sessions on Pro, Max, and Team plans will run in auto mode unless a user explicitly changes the setting, extending a rollout that already made auto mode the default on Bedrock, Vertex AI, and Foundry back in 2.1.207.
Why it matters
Anthropic flipping a default this broad signals real confidence in auto mode's guardrails, but it also means anyone who hasn't reviewed what auto mode actually permits is about to get it whether they asked for it or not. Worth checking your team's settings before the 14th.
How to use it
Review `auto-mode-config` settings before August 14th if your workflow depends on the previous manual-approval defaults, especially on shared Team plan seats.
Claude Code 2.1.257 Adds a Containment Escape Rule to Auto Mode
Claude Code 2.1.257 makes Claude Fable 5.1 the default Fable model and adds a Containment Escape rule so auto mode no longer auto-approves cloud metadata-credential fetches, egress evasion, or cross-tenant reach.
Claude Code v2.1.207: auto mode ships without opt-in on Bedrock, Vertex AI, and Foundry
Claude Code 2.1.207 turns on auto mode by default for Bedrock, Vertex AI, and Foundry users, removing the prior environment-variable opt-in requirement.
maxEffortLevel: One Setting to Throttle Every Model's Thinking Budget
Claude Code 2.1.267 adds a maxEffortLevel setting that caps the model effort level across every provider, including Bedrock, Vertex, and Foundry, while still letting users pick a lower level.