{"version":"2.1.257","anchor":"managedsettings-merge-mode-composition-rules-made-explicit","canonical_anchor":"managedsettings-merge-mode-composition-rules-made-explicit","heading":"managedSettings 'merge' mode composition rules made explicit and expanded","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/managedsettings-merge-mode-composition-rules-made-explicit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### managedSettings 'merge' mode composition rules made explicit and expanded\n\nManaged settings merge mode now documents which fields the helper replaces wholesale rather than merging.\n\nThe documentation for a helper's `managedSettings` `'merge'` mode now spells out per-field composition rules: helper scalars win, arrays union, and objects merge, except for a fixed list of fields \u2014 `fallbackModel`, `forceLoginOrgUUID`, `sandbox.filesystem.allowRead`, `sandbox.credentials.awsPairs`, `sandbox.ripgrep`, and restriction allowlists like `allowedMcpServers`, `availableModels`, and `allowedHttpHookUrls` \u2014 where the helper's value replaces the source's wholesale when it emits one. Permission tightening remains deny-only.\n\n- Area: Settings\n- Names: `fallbackModel`, `allowedMcpServers`, `allowedHttpHookUrls`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}