Start in auto mode by default
CHANGELOG · original
Changed interactive terminal and VS Code sessions to start in auto mode when no permission mode is configured, on every plan and provider; permissions.defaultMode still overrides it Open official changelog ↗ Documentation
Documentation excerpt
Auto mode on Bedrock, Agent Platform, or Foundry
On Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, and signed-in Claude apps gateway sessions, auto mode is available by default. If you don't set a permission mode there, interactive sessions start in auto mode, and claude -p or Agent SDK runs start in Manual mode, whose config value is default:
- Interactive terminal and VS Code sessions: to start them in a permission mode other than auto, set
permissions.defaultModeas Start in a different permission mode describes, or pick one from the VS Code extension's mode indicator. Which mode a session starts in lists the Claude Code versions that start them in auto mode. claude -pand Agent SDK runs: to start one in auto mode, pass--permission-mode autotoclaude -p, or passpermissionMode: "auto"in TypeScript orpermission_mode="auto"in Python. If you pass no permission mode, see Tool calls denied inclaude -pand Agent SDK runs, which also covers earlier Claude Code versions.
Only Claude Sonnet 5 or later, Opus 4.7 or later, Haiku 5.5, and the Fable models are supported on these providers. On any other model, the session starts in Manual instead. Auto mode with Haiku 5.5 on these providers requires Claude Code v2.1.293 or later.
To prevent developers from using auto mode, set disableAutoMode to "disable" in managed settings. This removes auto from the Shift+Tab cycle, and a session started with --permission-mode auto starts in Manual instead. A session already running in auto mode leaves it when the setting reaches that session from an admin-deployed source, and shows auto mode disabled by settings. Before v2.1.251, a running session kept auto mode until it ended.
Documentation snapshot · 2026-11-20