Skip to content
BENIBIX Learn

Project Settings File

AI⌨️ Claude CodeConfiguration

Also known as .claude/settings.json, shared project settings

A settings file in the repo. The whole team shares it in git.

Think of it like

It is like the rules on a class wall. All in that room follow them.

Example

Lucy commits a project settings file with a lint hook. Everyone who pulls the repo now gets the same hook.

Why it matters

It is how a team agrees on one setup. No one has to copy it by hand.

Definition

The project settings file is .claude/settings.json inside a repo. It is meant to be committed, so all who clone the repo get the same permissions, hooks and plugins. Claude Code reads it from the folder the session starts in. Some of what it sets waits until each person trusts the folder.

Example code

json
{
  "permissions": {
    "deny": ["Read(./.env)", "Read(./.env.*)"]
  }
}
Keep every teammate's Claude out of .env files.

Common mistake

Starting Claude in a subfolder and wondering why the rules are missing. It reads the file from where the session starts.

Key takeaways

  1. 1
    In the project. The .claude folder.
  2. 2
    Commit it. The team shares it.
  3. 3
    Waits for trust. Some keys.

Compare