One read of Claude Code CLIclaude-code-20260822T190701Z
1 pages moved out of 191 read.
Pages moved
1
significant first
Pages read
191
in this capture
Captured
19:07 UTC
Corpus hash
d4e49f423b70
corpus-hash
What this read moved
1-1 of 1plugins-reference Changed · +1 / -1 lines
from line 595
595595* **`--settings`**: the CLI flag or SDK inline settings
596596* **Managed settings**: [organization-controlled policy](/docs/en/permissions#managed-settings)
597597
598When more than one source sets the same key, managed settings take precedence, then `--settings`, then user settings. The [`--setting-sources`](/docs/en/cli-reference#cli-flags) flag narrows the list further.
598When more than one source sets the same key, managed settings take precedence, then `--settings`, then user settings. The only source you can remove from this list is user settings: pass [`--setting-sources`](/docs/en/cli-reference#cli-flags) without `user` and Claude Code skips them. Managed settings and `--settings` stay whatever you pass. The SDK's [`settingSources`](/docs/en/agent-sdk/claude-code-features#what-settingsources-does-not-control) option sets the same list.
599599
600600Entries in a project's `.claude/settings.json` or `.claude/settings.local.json` are ignored. Both files live in the workspace, so a cloned repository could supply values there, and those values would flow into plugin hook commands, MCP server configs, LSP commands, and monitor commands. Before v2.1.207, these entries were read. The restriction is specific to `pluginConfigs`: [`enabledPlugins`](/docs/en/settings-reference#enabledplugins) still honors project and local settings.
601601