Claude Code v2.1.232 ·
Rejected desktop overlay keys now say why
Refused gateway desktop overlay keys now come with a reason instead of vanishing.
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
New FeaturesKind: in v2.1.232,
New FeaturesSection of the release
What
When a gateway desktop overlay key is refused, the error explains the cause rather than dropping it silently.
Details
- Unknown keys suggest a typo or a newer Claude Desktop release; deprecated names point at their canonical key.
- Keys the gateway owns itself, such as OTLP relay and inference/upstream config, are reported as not settable through the overlay.
- 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.
Evidence
not operator-settable through the gateway desktop: overlay
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.232 →
