Claude Code permission modes explained (and when to use each)

Default, acceptEdits, plan, auto, dontAsk and bypassPermissions: what each Claude Code permission mode allows, how to switch, and which one fits which job.

· 5 min read

A Claude Code permission mode decides which actions run without asking you. Press Shift+Tab to cycle through them in a session, or start with claude --permission-mode <mode>. There are six: default, acceptEdits, plan, auto, dontAsk and bypassPermissions. Picking the right one is the difference between approving forty prompts a day and trusting something you should have read.

#What are the six permission modes?

ModeRuns without askingGood for
default (alias manual on the command line)Reads onlyReviewing every action yourself
acceptEditsReads, file edits, and common filesystem commands (mkdir, touch, mv, cp, sed, rm, rmdir) inside the working directoryIterating on code you will review afterwards
planReads; edits stay blocked until you approve a planExploring before changing anything
autoEverything, while a classifier model reviews actions in the backgroundLong tasks, fewer prompts
dontAskFile reads in working directories and pre-approved tools; anything that would prompt is deniedLocked-down scripts and CI
bypassPermissionsEverythingIsolated containers and VMs only

Two details are easy to miss. In acceptEdits, other shell commands still prompt, and so does anything outside the working directory (and the folders you added). And protected paths such as .git, .claude, shell rc files and .mcp.json prompt in default and acceptEdits rather than going through.

#How do you switch modes?

In a session, press Shift+Tab. The status bar shows where you are: ⏸ manual mode on, ⏵⏵ accept edits on, ⏸ plan mode on, ⏵⏵ auto mode on. The cycle runs default, acceptEdits, plan, with optional modes after. auto appears when it is available to you; bypassPermissions appears only if you enabled it at startup; dontAsk never appears in the cycle.

At startup:

claude --permission-mode plan
claude --permission-mode acceptEdits
claude --permission-mode dontAsk

As a default, in a settings file:

{
  "permissions": {
    "defaultMode": "acceptEdits"
  }
}

Settings precedence applies when several files set it. Note that auto and bypassPermissions set in a project's .claude/settings.json or .claude/settings.local.json have no effect: those belong in your user settings (~/.claude/settings.json) or in managed settings. That is deliberate, so a repository you clone cannot switch your safety off.

#When should you use acceptEdits or plan?

Use acceptEdits when you will review the result as a diff anyway. Refactors, test writing, renames and boilerplate are the classic cases: each edit is cheap to inspect afterwards, and approving them one by one is noise. Combine it with a clean git state so git diff shows exactly what changed. It does not cover arbitrary shell commands, so a curl | sh or a git push still asks.

Use plan before anything that touches several files or that you do not understand yet. Claude reads and explores, writes a plan, and cannot edit source until you approve it. It has its own article: plan mode in Claude Code.

#What does auto mode do, and is it safe?

In auto mode a separate classifier model reviews each action before it runs. It blocks actions that go beyond what you asked, that target infrastructure it does not recognize, or that look driven by hostile content Claude read (a prompt injection in a web page, say). Entering it drops broad allow rules such as Bash(*) or wildcarded interpreters, and restores them when you leave; narrow rules like Bash(npm test) stay. Three consecutive blocks or twenty in total pause it and bring the prompts back.

Availability depends on your plan, your model and your Claude Code version, and administrators can disable it, so check Shift+Tab on your machine. The docs are clear that it reduces prompts but is not a guarantee: use it where you trust the general direction of the task, not for sensitive operations.

#When is dontAsk the right choice?

For non-interactive runs where a prompt would hang or be meaningless. It denies everything that is not pre-approved, so you pair it with an explicit allowlist:

claude -p "run the test suite" \
  --permission-mode dontAsk \
  --allowedTools "Bash(npm test)" "Read"

If the job tries something outside the list, it fails instead of waiting for an answer nobody will give. See headless mode and CI in the usual docs; it is the right default for anything unattended.

#Is bypassPermissions ever okay?

Only in an environment that is already disposable: a container, a VM, a dev container without internet access. The docs say it offers no protection against prompt injection or unintended actions. Know what it still does and does not do:

  • Deny rules still block; allow rules have no effect.
  • Explicit ask rules, and some critical-path rm removals, still prompt.
  • Protected paths like .git and .claude become writable.
  • You cannot switch to it mid-session; it has to be enabled at launch with --permission-mode bypassPermissions or --dangerously-skip-permissions.
  • On Linux and macOS it refuses to start as root or under sudo unless it detects a sandbox.

If you run it on your laptop with your real credentials in reach, you are one bad web page away from a bad day.

#A practical way to choose

  1. New to the codebase or the tool: default, read what you approve. (Beginner's guide.)
  2. Unclear task: plan first, then switch.
  3. Well-understood edit, you will review the diff: acceptEdits.
  4. Long task in a repo you trust: auto, if you have it.
  5. Scripts and CI: dontAsk with an allowlist.
  6. Throwaway sandbox: bypassPermissions.

For rules that must always hold, whatever the mode, use permissions.deny in settings, or a hook; instructions in CLAUDE.md are guidance, not a lock.

#In Relais

Relais has a permission-mode picker in each session's composer with four choices: Ask, Accept edits, Plan and Full access, which map to default, acceptEdits, plan and bypassPermissions. Edits arrive as inline approval cards with their diff, and you can hide the picker in Settings if you always use the same mode. Session templates can also set the mode a session starts with. See features.

Claude Code,
better organized.

$14.99 a month, everything included. Mac and Linux, on your Claude Pro or Max plan. Cancel any time.