{"version":"2.1.265","anchor":"managed-settings-sources-helper-config-from-lower-priority","canonical_anchor":"managed-settings-sources-helper-config-from-lower-priority","heading":"Managed settings sources: helper config from lower-priority sources is now ignored with a warning when merged","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/managed-settings-sources-helper-config-from-lower-priority","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Managed settings sources: helper config from lower-priority sources is now ignored with a warning when merged\n\nWhen merging managed settings from multiple sources, policy-helper configuration from lower-priority sources is now ignored with a warning\n\n**What**\n\nWhen `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.\n\n**Why**\n\nPolicy 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.\n\n- Area: Managed Settings\n- Names: `managedSourcesBehavior`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}