Claude Code permission modes, and fewer prompts

Updated

Quick answer

Claude Code’s permission mode decides what it may do without asking, from Manual (default), which asks before most commands and edits, to bypassPermissions, which skips nearly every prompt. Since version 2.1.283, interactive sessions start in auto mode, where a classifier reviews actions instead of you. Allow, ask and deny rules refine any mode. To get fewer prompts without giving up control, allow the commands you run every day and keep a prompt for the rest.

What each mode does

Swipe the table sideways to see all columns.

ModeStatus barRuns without askingBest for
default (Manual)⏸ manual mode onReadsSensitive work, unfamiliar code
acceptEdits⏵⏵ accept edits onReads, file edits and common file commands such as mkdir, mv, cp, inside your working directoriesIterating on code you review with git diff
plan⏸ plan mode onReads and exploring; no edits until you approve a planUnderstanding a codebase before changing it
auto⏵⏵ auto mode onEverything, after a classifier checks each actionLong tasks, fewer prompts
dontAsk⏵⏵ don't ask onOnly what your rules pre-approve; everything else is deniedLocked-down scripts and CI
bypassPermissions⏵⏵ bypass permissions onEverything, apart from a few checks no mode skipsIsolated containers and VMs only

Manual mode is called default in settings and in hook input, and Claude Code accepts manual as an alias. Auto mode needs a supported model, and organizations can turn it off. Anthropic is plain about it: auto mode reduces prompts but does not guarantee safety.

Switch mode

Scripted runs differ: since version 2.1.302, claude -p starts in Manual mode when you set nothing, and a call that needs approval is denied unless a rule, a hook or --permission-mode auto approves it.

Allow, ask and deny rules

Rules sit on top of any mode. Allow lets a tool run without a prompt, ask always prompts, deny blocks. They are checked deny first, then ask, then allow, and the first match wins, however specific the others are. A rule is a tool name with an optional specifier:

~/.claude/settings.json

{
  "permissions": {
    "allow": ["Bash(npm run *)", "Bash(git commit *)", "WebFetch(domain:docs.python.org)"],
    "ask": ["Bash(git push *)"],
    "deny": ["Read(./.env)", "Bash(rm -rf *)"]
  }
}

A * stands for any text, so put it after the subcommand: Bash(git log *) allows only git log, while Bash(git *) allows every git command. Claude Code understands &&, | and ;, so Bash(npm test *) doesn’t approve npm test && curl …: every part must be allowed. Type /permissions to see all rules and the file each comes from. Choosing Yes, and don’t ask again at a prompt writes a rule for you. Deny rules hold in every mode, bypassPermissions included.

Fewer prompts, safely

The prompts that remain

Some prompts survive every mode: tools matched by an ask rule, Claude’s own questions (AskUserQuestion), and removals of critical paths such as your home folder. In Manual mode, so does everything you haven’t allowed. Permission prompts never resolve on idle, plan approval included: if you have stepped away, the session waits. To be told, add a Notification hook. To answer from wherever you are, a PermissionRequest hook can return the decision: Monish sends the prompt to your iPhone with Allow and Deny, and your deny rules still apply whatever you tap.

Questions

Which mode does Claude Code start in?
Interactive sessions in a terminal or VS Code start in auto mode since version 2.1.283, when auto mode is available, and in Manual mode otherwise. claude -p runs start in Manual mode since 2.1.302.
Why is auto in my project settings ignored?
defaultMode set to auto or bypassPermissions doesn’t take effect from a project’s .claude/settings.json or settings.local.json. Put it in ~/.claude/settings.json.
Is bypassPermissions safe?
Only in an isolated container or VM where Claude Code can’t cause damage. It skips nearly every prompt, including writes to .git and .claude.
Do deny rules apply in bypassPermissions mode?
Yes. Deny rules block in every mode. Allow rules have no effect in bypassPermissions, since everything is already allowed.

More guides

New to Monish? The home page shows what lands on your iPhone, and all guides are listed here.

Get Monish on your iPhone

Free, no account. Your 6-digit code is waiting in the app.

Download on the App Store