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.
| Mode | Status bar | Runs without asking | Best for |
|---|---|---|---|
default (Manual) | ⏸ manual mode on | Reads | Sensitive work, unfamiliar code |
acceptEdits | ⏵⏵ accept edits on | Reads, file edits and common file commands such as mkdir, mv, cp, inside your working directories | Iterating on code you review with git diff |
plan | ⏸ plan mode on | Reads and exploring; no edits until you approve a plan | Understanding a codebase before changing it |
auto | ⏵⏵ auto mode on | Everything, after a classifier checks each action | Long tasks, fewer prompts |
dontAsk | ⏵⏵ don't ask on | Only what your rules pre-approve; everything else is denied | Locked-down scripts and CI |
bypassPermissions | ⏵⏵ bypass permissions on | Everything, apart from a few checks no mode skips | Isolated 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
- During a session: press Shift+Tab. From auto, the cycle runs Manual, accept edits, plan, and back.
bypassPermissionsonly joins the cycle if you started with it available, anddontAsknever does. - From a prompt: in Manual and accept-edits mode, a Bash prompt can offer Yes, and switch to auto mode.
- For one session:
claude --permission-mode plan, ormanual,acceptEditsand the rest. - As your default:
"permissions": { "defaultMode": "default" }in~/.claude/settings.json. A project’s settings can set any mode exceptautoandbypassPermissions, which only count from your user settings. - In VS Code: the mode indicator under the prompt box, labelled Manual, Edit automatically, Plan, Auto and Bypass permissions.
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
- Allow what you run every day: tests, lint, build, local git commands. Common read-only commands already run without a prompt.
- Keep a prompt on what leaves your machine or can’t be undone:
git push, deploys, publishing, payments, with ask rules that hold even in auto mode. - Deny what must never happen: reading secrets, force pushes, deleting outside the project.
- Accept edits while you watch, and review with
git diffrather than one prompt per file. - Try the sandbox:
/sandboxwith auto-allow runs Bash commands without prompts inside an OS-level sandbox, on macOS, Linux and WSL2.
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
- The Claude Code PermissionRequest hookAnswer a permission prompt from a script: input, output, limits.
- Approve Claude Code permissions from your iPhoneHow a hook hands your Allow or Deny back to Claude Code.
- Long Claude Code tasks: how to step awayWhy long tasks stall, and how to keep one moving while you are out.
- How safe is approving Claude Code from a phone?Who can answer, what a tap can do, and what leaves your computer.
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.