Workbranch › Guides

How to manage permissions in Claude Code

Claude Code asks before it runs commands or edits files, and too many prompts slow you down while too few can be risky. This guide explains the prompts, the permission modes and the rules you can save, so you approve the routine work once and keep the dangerous parts blocked.

Updated 30 October 2026

This follows Anthropic's Claude Code documentation as of October 2026. New to Claude Code? Start with how to get started with Claude Code.

What Claude Code asks about

A prompt shows what Claude wants to do and your options. On most prompts you can move to Yes or No and press Tab to add a comment; with No, the comment reaches Claude as your reason and Claude keeps working with it in mind.

Pick a permission mode

Press Shift+Tab during a session to cycle through modes; the status bar shows which one is on. You can also start in one with claude --permission-mode plan.

Recent versions start interactive terminal and VS Code sessions in auto mode, and it works on all plans, with newer models only. To choose the starting mode yourself, set "defaultMode" under permissions in ~/.claude/settings.json. Auto and bypass set in a project's settings files are ignored, so a repository can't switch them on for you.

Save allow, ask and deny rules

1. In a session, type /permissions. The dialog lists every rule and which settings file it comes from, and lets you add or remove rules. Changes apply from Claude's next action.
2. Or edit a settings file directly. Shared rules for the team go in .claude/settings.json (commit it); your own go in .claude/settings.local.json or, for every project, ~/.claude/settings.json.
3. Write rules as Tool or Tool(pattern):
   • Bash(npm run *): any npm script
   • Bash(git commit *): commits, but not other git commands
   • Read(./.env): the project's .env file
   • WebFetch(domain:example.com): pages on that site
   • mcp__github__*: every tool from an MCP server named github

A typical starting point:

{"permissions": {"allow": ["Bash(npm run *)", "Bash(git commit *)"], "deny": ["Bash(git push *)", "Read(./.env)", "Read(./secrets/**)"]}}

Rules are checked in a fixed order: deny first, then ask, then allow. A deny always wins, even over a more specific allow, and an ask rule prompts even if an allow also matches.

Staying safe

• Put the * after the subcommand. Bash(git log *) allows only git log; Bash(git *) allows every git command, including ones that run other programs.
• Mind the space. Bash(ls *) doesn't match lsof; Bash(ls*) does.
• Command rules aren't a wall. A deny for Bash(rm *) doesn't stop bash -c 'rm …' or /bin/rm. Claude Code does split chained commands, so an allowed command followed by && and another one still needs every part allowed. For hard limits on files and network, use Claude Code's sandboxing.
• Block secrets with Read deny rules. In recent versions a Read deny also stops matching image paths you paste into the prompt from being attached, and hides matching names when you @-mention a folder.
• Protected files stay protected. Allow rules never pre-approve writes to places like .git, .claude, .mcp.json and shell files such as .zshrc. Outside bypass mode you're asked first, or in auto mode the classifier reviews the write.
• Turn risky modes off. Set permissions.disableBypassPermissionsMode or permissions.disableAutoMode to "disable" to stop them being used.

If it doesn't work

• An allow rule still prompts: a deny or ask rule from another settings file may match. Open /permissions to see each rule's source.
• A rule for another folder doesn't apply: Claude only works inside its working directories. Start with claude --add-dir path or list the folder in additionalDirectories.
• A path rule in user settings misses your project: paths starting with / in ~/.claude/settings.json are relative to ~/.claude. Use ~/ or // for absolute paths.
• The prompt has no "don't ask again": That option appears only when the prompt can list all that a saved rule would cover. Approve once, or write the rule yourself.

Sources

• Claude Code user FAQ (Claude Help Center, checked 30 October 2026)
• Configure permissions (Claude Code Docs, checked 30 October 2026)
• Permission modes (Claude Code Docs, checked 30 October 2026)

Frequently asked questions