{"version":"2.1.232","anchor":"gateway-desktop-policy-overlays-are-validated-before-serving","canonical_anchor":"gateway-desktop-policy-overlays-are-validated-before-serving","heading":"Gateway desktop: policy overlays are validated before serving","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/gateway-desktop-policy-overlays-are-validated-before-serving","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Gateway `desktop:` policy overlays are validated before serving\n\nGateway operators get startup errors for bad desktop policy keys instead of silently passing them through.\n\n**What**\n\nIf you run a Claude gateway and your config sets `managed.policies` entries with a `desktop` block, those settings are now checked against Claude Desktop's managed-configuration schema at startup. Unknown keys, keys the gateway is not allowed to serve, unparseable values and values Desktop would silently discard now abort startup with a per-key error list instead of being passed through untouched.\n\n**Details**\n\n- The previous build shallow-merged `{ match, cli, desktop }` and served whatever was written.\n- Non-fatal findings, such as reports of dropped values and intake warnings, are logged as warnings and do not stop startup.\n\n**Evidence**\n\n`desktop overlay invalid: refused or unparseable keys`\n\n- Area: Managed Settings\n- Names: `managed.policies`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}