Skip to content
BENIBIX Learn

Claude Code Settings Precedence

AI⌨️ Claude CodeConfiguration

Also known as settings precedence, settings order

The order that says which file wins when two set the same key.

Think of it like

It is like asking a parent and then a teacher. The higher one has the last word.

Example

Lucy set a model in her user file, but Claude keeps using another. The project file sets one too, and it is higher.

Why it matters

When a setting seems to be skipped, this order nearly always says why.

Definition

Settings precedence is the order Claude Code uses when two files set the same key. From top to bottom it is managed settings, the command line, the local file, the shared repo file and your user file. The top one that sets a key wins. Lists such as permissions.allow are not like that. They merge, so each file adds its own lines.

Example code

bash
claude --settings '{"model": "claude-opus-5-5"}'
A flag sits above your files, for this one session.
Read it top down: the first level that sets a key wins.

Common mistake

Thinking a deny rule in a lower file is lost. Lists of rules merge, so each file's rules still count.

Key takeaways

  1. 1
    Five levels. Managed on top.
  2. 2
    Highest wins. For one key.
  3. 3
    Lists merge. Rules add up.