Learn one feature at a time
Choose how much
Claude can do.
Compare all six permission modes and identify the controls available in your interface.
Start with this comparison
| Mode | Approval behavior | Suggested use |
|---|---|---|
Manual (default) | Prompts according to tool rules; built-in read-only actions can run without prompts. | Learn what each action does. |
| Plan | Analyze before edits; command execution still depends on permissions. | Explore unfamiliar changes. |
| Accept Edits | Approve supported file edits and common filesystem commands automatically. | Review a small agreed change. |
| Auto | Background checks decide many actions instead of asking you. | Bounded work with reviewed access. |
dontAsk | Deny actions that would need a prompt. | Advanced automation with explicit allowances. |
bypassPermissions | Skip permission checks. | Isolated environments only; avoid as a beginner. |
Cloud sessions offer Auto, Accept Edits, and Plan. The six-mode list describes Claude Code overall, not six choices in every interface.
Why a session may already say Auto
Auto is now the built-in starting mode for eligible Pro, Max, and Team sessions. It is not universal: saved choices, versions, providers, and organization controls can change it. Check the mode shown beside your prompt before sending work. The built-in Auto default requires v2.1.228 or later on macOS, Linux, and WSL, or v2.1.233 on native Windows.
Starts in Manual unless overridden: Enterprise, Console API-key sessions, print mode (claude -p), and sessions using Bedrock, Google Cloud Agent Platform, or Microsoft Foundry. An unavailable Auto mode also falls back to Manual. Setting "auto" in project .claude/settings.json or .claude/settings.local.json does not take effect; use the supported user or managed setting and check the session indicator. Defaults in the VS Code extension and Desktop have their own precedence rules.
A practical first session
- Choose a practice repository.
- Check the active mode and select Plan to explore.
- Ask for a small proposed change and how to test it.
- Review the plan, then select an editing mode deliberately.
- Inspect the diff and test results before publishing.
Model choice and permission mode do different jobs. A model is the reasoning engine; a permission mode controls how actions are approved. Neither replaces backups or review.
References
- Anthropic. (n.d.-f). Choose a permission mode. Retrieved September 24, 2026, from https://code.claude.com/docs/en/permission-modes
- Phillippi, C. (2026, August 7). Auto mode is now the default in Claude Code for Pro, Max, and Team plans. https://claude.com/blog/auto-mode-default-in-claude-code
Was this chapter useful?
Report an errorVotes are shared only if you enable optional measurement in Privacy & Preferences.