Auto mode permissions workflow
Instructions
- Choose auto mode when you want fewer permission interruptions than the default mode but more safeguards than --dangerously-skip-permissions.
- Enable auto mode with
claude --enable-auto-mode, then switch permission modes within a session (e.g., Shift+Tab) as needed. - Expect auto mode to automatically approve actions that look safe while blocking actions that look risky; if actions are repeatedly blocked, be ready to approve a prompt or adjust the plan.
- Use isolated environments when running long tasks, and treat auto mode as risk-reducing rather than risk-eliminating.
- If you are an admin and need to prevent use of auto mode, set the managed setting
disableAutoModeto disable it.
Examples
User: "Refactor the project to use the new config format across all packages; keep tests passing."
Assistant: "I will enable auto mode to reduce approval interruptions during the multi-file changes, and I will avoid any mass-deletion commands."
User: "Run a long migration script and update docs. Stop and ask if anything looks destructive."
Assistant: "I will proceed in auto mode for routine edits, and I will pause for confirmation if the classifier blocks an action repeatedly."
Source
Distilled from Auto mode for Claude Code (published 2026-03-24).