Skip to content
BENIBIX Learn

--settings Flag

Also known as claude --settings, Inline settings

It loads extra settings for one session from JSON.

Think of it like

It is like a note for just today. It says, wear the red shirt.

Example

Emma's CI keeps one settings file with its own permission rules. Each job starts claude with --settings pointing at it, and no one's own files change.

Why it matters

A run can get its own settings, and no one has to edit the shared files.

Definition

--settings loads extra settings for this session, from a JSON file or a JSON string. Its values win over the same keys in your settings.json files. Keys it leaves out keep their usual values. Your admin's managed settings still win over it. The file must be a normal file of 2 MiB or less.

Example code

bash
claude --settings ./ci-settings.json
Use the CI settings for this run only.
This flag is the second layer, just under the admin's.

Common mistake

Expecting it to beat managed settings. Your admin's rules still come first.

Key takeaways

  1. 1
    File or string. JSON.
  2. 2
    Wins over your files. For these keys.
  3. 3
    Managed still wins. Over it.

Compare

Learn it properly