settings.json vs settings.local.json
People think settings.local.json is a backup of settings.json. It is a second file with a different owner. The project file is shared in git, so it sets the rules for the whole team. The local file is yours alone, stays out of git, and wins when both set a key. Rules you approve from a prompt are saved in the local one.
Project Settings File
A settings file in the repo. The whole team shares it in git.
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.
Local Settings File
Your own settings for one project, kept out of git.
The local settings file is .claude/settings.local.json inside a project. It holds your own changes for that one project and sits above the shared project file, so it wins when both set a key. When you choose Yes, and don't ask again on a prompt, Claude Code saves the rule here. When Claude Code makes the file, it keeps it out of git for you.
In one line
- Project Settings File
- A settings file in the repo. The whole team shares it in git.
- Local Settings File
- Your own settings for one project, kept out of git.