Features · Built in · since version 0.2.67
Settings
Configure Claude Code with JSON settings files for you, your project and your team.
What it is
Settings control things like the model, permission rules, hooks and environment variables. They live in JSON files at several levels: your user file for every project, a project file committed for the team, a local project file just for you, and managed settings an organization can enforce. When files disagree, the more specific or more official level wins, while lists such as permission rules are combined.
Why it matters
- One setup for the whole teamCommit .claude/settings.json and everyone gets the same permission rules and hooks.
- Personal tweaks stay personal.claude/settings.local.json holds your own overrides and is not shared.
- Organization guardrailsManaged settings sit above every other level, so company rules can't be switched off locally.
How it works
- Put settings for all projects in ~/.claude/settings.json.
- Put shared project settings in .claude/settings.json and your own in .claude/settings.local.json.
- Change a value from inside a session with /config, for example /config verbose=true.
- Order, highest first: managed, command line (--settings), local project, shared project, user.
- Run /status to see which files were loaded; files must be strict JSON, without comments or trailing commas.
Hands-on example coming
This feature has no reviewed example yet. The official documentation below has the details.
Update history
Version 1.0.7 · May 30, 2025
Updated Settings moved into settings.json files, replacing the claude config commands.
Version 0.2.67 · Apr 9, 2025
Introduced Shared project rules could be saved in .claude/settings.json.