Seongwoo Choi / Journal

Claude Code permission settings order: How deny, ask, and allow rules are applied

At a glanceClaude Code often asks for approval when modifying files or running commands. Check which actions require approval and the order in which saved rules apply to reduce mistakes.

Conceptual illustration for Claude Code permission settings order: How deny, ask, and allow rules are applied.
AI-generated editorial illustration; not a product screenshot.
In this article 6 sections
  1. 1. Distinguish actions that require approval from those that do not
  2. 2. Check where “Yes, don’t ask again” rules are saved
  3. 3. Rule application order: deny, ask, allow
  4. 4. Define the scope of deny rules
  5. 5. Choose a permission mode
  6. 6. Criteria to remember

Claude Code can modify files and run commands, so approval prompts often appear when you first use it. Before habitually clicking the approval button, check which actions require approval and the order in which saved rules are applied to reduce mistakes. The following is based on a reading of Anthropic’s official permissions documentation as of October 31, 2026. It is not the result of changing settings and testing them directly.

1. Distinguish actions that require approval from those that do not

The documentation table shows that reading and searching files in the working directory run without approval. By contrast, Bash command execution, file modification, fetching web pages (WebFetch), and web searches (WebSearch) require approval by default. However, read-only Bash commands specified in the documentation are exceptions. The basic practice is to read the entire command string shown in the approval prompt before clicking.

2. Check where “Yes, don’t ask again” rules are saved

When you choose “Yes, don’t ask again” in an approval prompt, the Bash command or web-fetch domain is saved as a rule. It is saved in .claude/settings.local.json at the root of the Git repository, and the same rule applies to sessions started in subfolders or worktrees. File-modification approvals are not saved to a file and remain valid only until the session ends. You can see the rules in the /permissions screen, along with the source file for each rule.

3. Rule application order: deny, ask, allow

Rules are evaluated in the order deny, ask, allow, and the first matching rule determines the result. Therefore, placing a narrow allow rule inside a broad deny rule does not create an exception. For example, in the documentation, if there is a broad deny rule such as Bash(aws *), the call is still blocked even if there is an allow rule for Bash(aws s3 ls). The diagram below summarizes this order.

4. Define the scope of deny rules

If you deny only the tool name—for example, by denying Bash entirely—the model cannot see that tool at all. If you want to block only specific commands, use a scoped rule such as Bash(rm *). In that case, the tool remains available and only matching calls are blocked. The documentation says that rules added in /permissions apply starting with the next tool call in the same turn.

5. Choose a permission mode

The default mode asks for approval the first time each tool is used. acceptEdits automatically approves file modifications in the working directory and commands such as mkdir, touch, mv, and cp. plan explores primarily through reading without modifying files. dontAsk rejects calls that require approval without asking. bypassPermissions skips confirmation prompts, so the documentation warns that it should be used only in isolated environments such as containers or virtual machines. In auto mode, a classifier reviews the action, and availability depends on the account and settings.

6. Criteria to remember

Permission rules are enforced by Claude Code. Writing “Do not delete” in a prompt or CLAUDE.md only communicates the intended direction of the work; it does not block access. To actually block access, use deny rules, a permission mode, or a PreToolUse hook. For settings shared with a team, commit them to the repository, and manage settings.local.json, which contains personal approval records, separately.

Recommended reading: Claude Code installation and first login: Steps to check , Checklist for removing personal information before uploading documents to AI

Reference: Claude Code official documentation, Configure permissions

Sources and original article

Read the Korean original on Naver

This article reflects public information available when it was written. Specifications, prices and schedules can change; check the linked official documentation.

This English edition was written and translated with AI assistance, with sources provided. For errors or additional information, please request a correction. Editorial policy