{"version":"2.1.232","anchor":"rejected-desktop-overlay-keys-now-say-why","canonical_anchor":"rejected-desktop-overlay-keys-now-say-why","heading":"Rejected desktop overlay keys now say why","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/rejected-desktop-overlay-keys-now-say-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Rejected desktop overlay keys now say why\n\nRefused gateway desktop overlay keys now come with a reason instead of vanishing.\n\n**What**\n\nWhen a gateway `desktop` overlay key is refused, the error explains the cause rather than dropping it silently.\n\n**Details**\n\n- Unknown keys suggest a typo or a newer Claude Desktop release; deprecated names point at their canonical key.\n- Keys the gateway owns itself, such as OTLP relay and inference\/upstream config, are reported as not settable through the overlay.\n- Empty-string and null values are flagged, with a specific message that a role policy cannot blank out a key set by the catch-all base entry.\n\n**Evidence**\n\n`not operator-settable through the gateway desktop: overlay`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}