managedSourcesBehavior
A Claude Code settings key, read out of the shipped bundle. It has been in the build since v2.1.242, including the newest one read.
What it is
Compose every [managed source](/docs/en/managed-settings#how-claude-code-combines-managed-sources) you deploy instead of using the highest-priority one alone
Anthropic's own wording. Read off Claude Code settings reference, captured 2026-08-28.
Presence across releases
| Releases | Reading | Declared type | Default |
|---|---|---|---|
| 2.1.245 – 2.1.250 5 releases | never mined | — | — |
| 2.1.242 – 2.1.243 2 releases | in the build | — | — |
A row reading never mined is a release with no archived bundle behind it. Nothing was read out of it, so nothing here says whether the name was in it. A declared type or a default is only ever what that release's own bundle stated.
Changelog entries naming it
-
v2.1.248Two new settings keys named: WSL settings inheritance and managed-source behaviour
Two settings keys are named for WSL inheriting Windows settings and managed-source behaviour.
named in this entry
-
v2.1.242Managed settings can now merge across sources instead of the top one winning
Admins can set managedSourcesBehavior to merge managed settings sources instead of only the top one.
named in this entry
Documentation pages
- Claude Code settings reference reference table Claude Code CLI
- Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry mentions it Claude Code CLI
- Deploy managed settings mentions it Claude Code CLI
A reference table page is one whose own table defines this name, and it is where the description above came from. A page that mentions it carries the name somewhere in its text and may say nothing about it at all. Every page carrying it.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.