Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Rejected desktop overlay keys now say why

You'll notice
Useful1 Signal1
Managed Settings

Refused gateway desktop overlay keys now come with a reason instead of vanishing.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →