Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code 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

You'll notice Improvements
JSON All of v2.1.265
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What

When managedSourcesBehavior is set to "merge" (composing every managed settings source, such as MDM or a managed settings file, instead of only using the highest-priority one), policy-helper configuration keys found in a non-highest-priority source are now explicitly ignored, and Claude Code surfaces a warning about it. Previously this configuration would silently merge in.

Why

Policy helper configuration is now read only from the highest-priority managed settings source. The warning makes this explicit instead of letting an admin believe a lower-priority source's helper settings were taking effect when they weren't.

Read from
Names in the bundlemanagedSourcesBehavior
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Configure server-managed settings touched a line naming managedSourcesBehavior after this was published. * **Gateway sign-in keys**: Claude Code never reads [`forceLoginGatewayUrl`](/docs/en/settings-reference#forcelogingatewayurl), [`gatewayInternalNetworks`](/docs/en/settings-reference#gatewayinternalnetworks), or the `"gateway"` value of [… server-managed-settings see the edit
Confirmed since Anthropic's documentation has since written up managedSourcesBehavior, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry. The hooks lock and `allowManagedPermissionRulesOnly`'s effect on the developer's own rules need the winning source by default; under the `managedSourcesBehavior` merge opt-in in [how Claude Code combines managed sources](/docs/en/managed-s… claude-apps-gateway see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up managedSourcesBehavior, on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS…

See this entry in the whole of v2.1.265 →

Feedback