✻Founding-member pricing: every lesson for $19/mo. The first 3 lessons are free. Start lesson 1 →
Unit 3 · Configure Claude · Lesson 14 of 40

Permission Modes: Choosing the Right Autonomy

Learn all six Claude Code permission modes (Manual, acceptEdits, plan, auto, dontAsk, bypassPermissions) and pick the right one for each job.

ACADEMY12 min+74 XP5-question quiz

🎯 By the end of this lesson you'll be able to

  • Describe what each permission mode allows without asking
  • Switch modes in the CLI, VS Code and desktop
  • Match modes to tasks and environments
  • Know what no mode will ever auto-approve

Autonomy is a dial

How much should Claude do without asking? It depends on the task, the codebase and where it's running. Permission modes are the dial.

ModeRuns without askingBest for
default (Manual)Reads onlySensitive work, reviewing every action
acceptEditsReads, file edits and common file commands in your working directoriesIterating while you review the diff
planReads and research. No edits.Exploring before changing anything
autoMost actions, with a background classifier checking each oneLong tasks with fewer interruptions
dontAskOnly pre-approved tools. Everything else is denied.Locked-down CI and scripts
bypassPermissionsEverythingIsolated containers and VMs only

Switching modes

  • CLI: Shift+Tab cycles Manual → Accept edits → Plan, and on to Auto when it's available.
  • VS Code: the mode indicator in the prompt box.
  • Desktop: the mode selector.
  • At launch: claude --permission-mode acceptEdits
  • As a default: "permissions": { "defaultMode": "acceptEdits" } in settings.

Auto mode, honestly

Auto mode lets Claude work through long tasks with few prompts while a separate classifier model reviews each action in the background and blocks the risky ones. Recent versions use it as the starting mode for interactive terminal and VS Code sessions. It's a big productivity win, but it's a safety net, not a guarantee. Pair it with deny rules for anything that must never happen, and work on a branch.

!
bypassPermissions is for sandboxes

bypassPermissions (also --dangerously-skip-permissions) runs everything without asking. Use it only inside isolated, disposable environments like containers or VMs with no access to production credentials. Never on your daily machine.

What no mode auto-approves

Some safeguards hold in every mode:

  • Deny rules block in every mode, even bypassPermissions.
  • **Explicit ask rules** still ask.
  • Questions Claude needs you to answer still come to you.
  • Dangerous deletions of critical paths aren't silently approved.

Pick the mode

◎Which mode fits?pick the best fit
You're exploring an unfamiliar repo and don't want anything changed yet.
Research and proposals, no edits.
A nightly CI job should run only pre-approved lint and test commands and fail closed otherwise.
Anything not pre-approved is denied, which is perfect for locked-down automation.
You're iterating on a UI component and reviewing each diff as it lands.
Edits flow freely while you watch the diff.
A long, well-scoped refactor where constant prompts would slow you down.
The classifier checks actions in the background while Claude keeps moving.
You're touching payment code in production-adjacent config.
Manual approval keeps eyes on every action.
A throwaway container running an experimental agent with no secrets.
Only acceptable in isolated, disposable environments.
⌨Type the command+15 XP

Start a session where file edits are accepted automatically. Type the full command.

❯

Check your understanding

?Lesson quiz10 XP per correct answer · +25 for a perfect score
QUESTION 1 OF 5

Which mode denies anything that isn't pre-approved?

Why: dontAsk is designed for locked-down CI and scripts.
QUESTION 2 OF 5

Where is bypassPermissions appropriate?

Why: It skips all prompts, so use it only in disposable sandboxes.
QUESTION 3 OF 5

Do deny rules apply in bypassPermissions mode?

Why: Deny rules are the one control every mode respects.
QUESTION 4 OF 5

What checks actions in auto mode?

Why: A separate classifier reviews actions. It's a strong safety net but not a guarantee.
QUESTION 5 OF 5

Which key cycles modes in the CLI?

Why: Shift+Tab cycles through the available modes.
0 / 5 correct
Academy lesson

Unlock lesson 14 and the next 26

You've finished the free lessons. Join the Academy for $19/month to unlock every lesson, quiz, terminal simulation and puzzle, plus the final exam and your certificate of completion.

  • All 40 lessons across 9 units
  • 165+ quiz questions
  • Final exam + certificate
  • New lessons as Claude Code evolves
  • XP, streaks and badges
  • Cancel anytime

Already a member? Log in to continue.

Key takeaways

  • Modes are an autonomy dial: Manual → acceptEdits → plan → auto → dontAsk → bypass.
  • Match the mode to the task and the environment.
  • Auto mode is a safety net, not a guarantee. Pair it with deny rules and branches.
  • Deny rules hold in every mode. bypassPermissions is for sandboxes only.

Nice work. Lesson 14 done?

Mark it complete to earn +74 XP, keep your streak alive and unlock badges.

Written by Curtis Cornell from Anthropic's public Claude Code documentation. Last reviewed November 14, 2026. Claude Code changes fast; if something here differs from your version, the official docs win.

Start lesson 1 free →