{"version":"2.1.321","anchor":"gateway-desktop-overlay-validation-rejects-unknown-nested-fi","canonical_anchor":"gateway-desktop-overlay-validation-rejects-unknown-nested-fi","heading":"Apps gateway refuses desktop policy entries that Claude Desktop cannot read","tier":"notice","area":"Gateways","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/gateway-desktop-overlay-validation-rejects-unknown-nested-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Apps gateway refuses desktop policy entries that Claude Desktop cannot read\n\nThe apps gateway now refuses to serve a desktop policy entry with unknown fields that Claude Desktop would drop or misread, instead of only warning\n\n**What**\n\nThe apps gateway serves a desktop policy overlay, which is a set of settings layered on top of Claude Desktop's own. It now checks any unknown fields in that overlay against the Claude Desktop schema it carries. A schema is the list of fields and values Claude Desktop understands.\n\nIf a field is unknown to that schema and Claude Desktop would drop or misread the entry or key holding it, the gateway refuses to serve the entry. Before, unknown keys only produced a warning.\n\n**Why**\n\nGateway administrators can now get hard errors from configuration that was accepted before. Check overlays for fields Claude Desktop does not recognise before rolling this out.\n\n- Area: Gateways\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}