Claude Code
Claude Code: allow commands without prompts (permission modes and allow rules)
How do I stop Claude Code asking for permission every time?
Press Shift+Tab to cycle permission modes, start with claude --permission-mode <mode>, or pre-approve specific commands with permissions.allow rules such as Bash(npm run *) in .claude/settings.json. Auto mode runs without routine prompts while a classifier reviews actions; --dangerously-skip-permissions is meant only for containers or VMs.
Permission modes
- default (labeled Manual): prompts on first use of each tool.
- acceptEdits: auto-accepts file edits and common filesystem commands such as mkdir, touch, mv and cp in your working directories.
- plan: explores and runs read-only commands but doesn't edit your source files.
- auto: no routine prompts; a background classifier checks shell commands and network requests against your request. It is the built-in starting mode from v2.1.283.
- dontAsk: denies anything that would prompt, except tools you pre-approved.
- bypassPermissions: skips prompts, including writes to protected paths like .git and .claude. Only for isolated containers or VMs.
Switch modes
- During a session: press Shift+Tab to cycle default → acceptEdits → plan (and other enabled modes).
- For one session: claude --permission-mode plan (or default, acceptEdits, auto, dontAsk).
- As a default: set permissions.defaultMode in ~/.claude/settings.json.
Pre-approve exact commands instead
Allow rules are safer than skipping all checks. Put the * after the subcommand: Bash(git log *) allows only git log, while Bash(git *) allows every git command. Deny rules always win.
.claude/settings.json
{
"permissions": {
"allow": ["Bash(npm run *)", "Bash(git commit *)"],
"deny": ["Bash(git push *)"]
}
}Use /permissions inside Claude Code to see every rule and which settings file it comes from.
Fully unattended runs
Only inside a container or VM, as a non-root user
claude -p "run the test suite and fix failures" --dangerously-skip-permissions
Sources
More on Claude Code
Other guides
Get the weekly agent stack update
New official MCP servers, spec changes and harness releases, checked against the source. One email a week, no fluff.
Reviewed Oct 6, 2026. Settings change often; the linked vendor docs are the source of truth.