managedSourcesBehavior
A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.242 and was gone by v2.1.284.
Compose every managed source you deploy instead of using the highest-priority one alone
Anthropic's own wording. Read off All settings, captured 2026-10-22.
In the changelogs
6Releases whose published page names managedSourcesBehavior.
-
v2.1.300
Cowork cloud keeps strict managed policy settings once they are set
In Cowork cloud, once certain managed policy settings are tightened, a later settings update can no longer loosen them
found in this entry's text
-
v2.1.265
Managed settings sources: helper config from lower-priority sources is now ignored with a warning when merged
When merging managed settings from multiple sources, policy-helper configuration from lower-priority sources is now ignored with a warning
found in this entry's text, named in this entry
-
v2.1.265
policyHelpers per-source shadowing warning gated behind
managedSourcesBehavior: "merge"Claude Code now warns when multiple managed settings sources define conflicting policy helper config under merge mode
found in this entry's text, named in this entry
-
v2.1.248
Module initialisation moved from first use to startup
Nearly all modules now load their code at startup instead of on first use, shifting timing.
found in this entry's text
-
v2.1.248
Two 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, found in this entry's text
-
v2.1.242
Managed 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, found in this entry's text
First cited
5The earliest release whose published evidence quoted managedSourcesBehavior was v2.1.242, 24 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
2Build by build
56One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
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.