Claude Code auto mode is now the default on enterprise clouds
Claude Code v2.1.207 removes the opt-in for auto mode on Bedrock, Vertex AI, and Foundry, and upgrades the default model to Opus 4.8.
Anthropic shipped Claude Code v2.1.207 on July 12, making auto mode the default on AWS Bedrock, Google Cloud Vertex AI, and Anthropic Foundry. Previously, teams on these platforms had to set the CLAUDE_CODE_ENABLE_AUTO_MODE environment variable to unlock the behavior. That opt-in is now gone.
The same release upgrades the default model on Bedrock, Vertex, and Foundry from Claude Opus 4.7 to Claude Opus 4.8. Opus 4.8 ships improved agentic judgment, more efficient tool calling, and stronger computer-use performance compared to 4.7.
What auto mode does
Auto mode lets Claude Code decide its own permission level mid-task rather than waiting for a human to approve each action. It starts conservative, requests elevated permissions when it needs them, and documents what it is doing and why. For teams running coding agents, long multi-step tasks (refactors, test generation, multi-file changes) complete without the operator approving each prompt.
Auto mode became available on Bedrock and Vertex in May 2026, but required the environment variable to activate. Enterprise teams, particularly those working inside AWS or GCP governance frameworks, reported the opt-in as the most-requested configuration change since Claude Code launched. Removing it makes the enterprise cloud experience match what direct Anthropic API users have had since the mode shipped.
What to check before upgrading
If your organization runs Claude Code with explicit permission-mode flags (--permission-mode manual or --permission-mode acceptEdits), nothing changes. Those flags override the default and will continue to work the same way.
If you run Claude Code without specifying a permission mode on Bedrock or Vertex and want to preserve the previous manual-review behavior, add --permission-mode manual to your invocation before upgrading to v2.1.207.
Teams using hooks or SDK integrations that set defaultMode explicitly are also unaffected. Only bare invocations that relied on the opt-in being absent will notice the change.
For a full rundown of how auto mode fits into agent permission planning, see running coding agents remotely and when you let an AI spend money.