Skip to content
BENIBIX Learn

Edit Permission Rule

AI⌨️ Claude CodeConfiguration

Also known as Edit(src/**), Edit allow rule

A rule that says which files Claude may change.

Think of it like

It is like you let a friend draw in one book. The rest stay shut.

Example

Emma lets Claude change code in src freely. She denies the CI folder, so those files stay hers.

Why it matters

Edits change your project. These rules choose which changes are routine and which need a look.

Definition

An Edit permission rule matches the files that Claude may change in your project. It is written as Edit and a path, such as Edit(src/**). It covers every built-in tool that edits files, including Write. It also covers where a shell command writes with > or tee. A rule written as Write(path) does not match, so always use Edit.

Example code

json
{
  "permissions": {
    "allow": ["Edit(src/**)"],
    "deny": ["Edit(.github/**)"]
  }
}
Edit code freely, never the CI files.

Common mistake

Writing Write(docs/**). It is accepted but matches nothing. Write Edit(docs/**).

Key takeaways

  1. 1
    Edit and a path. Edit(src/**).
  2. 2
    All edit tools. Write too.
  3. 3
    Redirects count. > and tee.

Compare