Features · Built in · since version 0.2.21

Permissions

Decide which actions Claude Code may take on its own, which need your OK, and which are never allowed.

What it is

Before Claude edits a file, runs a command or uses a tool, Claude Code checks your permission rules. Each rule names a tool, optionally narrowed down, such as Bash(npm run test *) or Read(./.env), and sits in one of three lists: allow, ask or deny. A permission mode sets the overall behaviour, from asking about everything to accepting file edits automatically.

Why it matters

  • Fewer interruptionsAllow the commands you run all the time, such as tests and linters, and Claude stops asking about them.
  • Hard limitsA deny rule always wins, so secrets files or risky commands stay off limits whatever else is allowed.
  • The right pace for the taskSwitch modes with Shift+Tab: review each edit, accept edits automatically, or only plan.

How it works

  1. When Claude asks, choosing "don't ask again" saves an allow rule for that project.
  2. Use /permissions to see, add and remove rules, or edit the permissions block of a settings file.
  3. Rules are checked in the order deny, then ask, then allow; the first match decides.
  4. Pick a starting mode with --permission-mode or the defaultMode setting, and cycle modes in a session with Shift+Tab.
  5. Bash rules match command text, so they are a convenience, not a security boundary; use deny rules and the sandbox for protection.

Hands-on example coming

This feature has no reviewed example yet. The official documentation below has the details.

Update history

  1. Version 1.0.72 · Aug 8, 2025

    Updated Ask rules: always confirm before chosen tools run.

  2. Version 1.0.7 · May 30, 2025

    Updated The /allowed-tools command was renamed /permissions.

  3. Version 0.2.21 · by Mar 4, 2025

    Introduced Already part of Claude Code when the changelog began with this version.

Official documentation