Auto mode
Full Lesson Reference
Auto mode lets Claude Code work continuously without stopping at every permission prompt. Instead of approving each action, you approve the session once and let Claude execute autonomously until it hits something that needs explicit confirmation.
Useful. Also risky if used wrong. This lesson covers when to turn it on, when to leave it off, and the rails that stay on even in auto mode.
What auto mode actually is
Auto mode is a runtime setting that reduces interruption for low-risk work. With auto mode on:
- Claude executes file edits, reads, and routine operations without asking
- Claude still pauses for destructive actions, shared infrastructure, and external effects
- You can toggle it on or off mid-session
- Settings reset at session end
The goal: remove the constant interruption of approving every tiny action, without removing the safety rail around actions that actually matter.
When auto mode is appropriate
Routine daily work you've done many times before
- Building a weekly report in a familiar template
- Writing emails in a style Claude already knows
- Editing landing page copy inside a project you set up
- Running audits using a skill you've used successfully before
Batch work where interruptions waste time
- Editing 30 files in the same pattern
- Creating multiple versions of ad copy
- Processing a list of items through the same workflow
Trusted skills you've validated
If you've run a skill 10 times and know exactly what it does, auto mode through that skill is fine. Claude's still working inside the guardrails the skill defined.
When auto mode is NOT appropriate
First time running a workflow or skill
You don't know what to expect. You need to see every decision Claude makes so you can catch mistakes before they compound. Leave auto mode off until you've done the workflow 2-3 times with full permission prompts.
New platforms or new integrations
Just connected a new MCP? New database? New client account? Keep auto mode off. Let Claude ask permission until you've seen what a typical interaction looks like.
Production systems or client-facing work
Live websites, active ad campaigns, client databases. Anything with real customers downstream. The interruption is a feature, not a bug.
Work that touches money or sends communications
Auto mode plus anything that emails, posts, charges, or mutates ad platforms is a recipe for expensive mistakes. Always leave auto mode off for these.
How to turn auto mode on
In your Claude Code session, tell Claude
Turn on auto mode
Claude confirms and switches modes. You'll stop getting permission prompts for routine actions.
How to turn it off
Tell Claude
Turn off auto mode
Or end the session (close the terminal) - auto mode resets every session, so a new Claude Code session always starts with it off.
What stays protected even in auto mode
Auto mode doesn't remove every safety check. These still trigger a prompt:
- Destructive operations (delete, drop, force push, rm -rf)
- Pushing to shared branches
- Operations outside your project folder
- External API calls that cost money or affect customers
- Operations involving credentials or secrets
- Mutations in ad platforms (create, pause, modify campaigns)
Auto mode removes friction for routine work. It doesn't remove the rails around the work that matters.
The honest trade-off
Auto mode makes you faster. It also makes mistakes cheaper to make. The question isn't "is auto mode good or bad" - it's "am I running the kind of work where a cheap mistake is acceptable?"
- Building a draft for internal review - cheap mistakes are fine, auto mode on
- Running a skill you wrote yourself - medium risk, judgement call
- Shipping to production or client systems - expensive mistakes, auto mode off
Default to off. Turn it on when you know the work is routine and bounded.
Action items
☐ Understand what auto mode skips and what it still prompts for
☐ Default to auto mode OFF for the first month while you learn
☐ Turn it on only for routine / batch work you've done before
☐ Always turn it OFF when touching production, ads, or emails
☐ Remember: auto mode resets every session. Starting fresh = starting safe.
Next lesson: Dangerous mode - what it is and why you shouldn't use it.
Exercises
- Review the concepts covered in this lesson: Auto mode.
- Write down your key takeaway from this lesson.
- Practice running any commands or prompts mentioned above inside your terminal.