Source Intelligence

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

Gateway desktop: policy overlays are validated before serving

You'll notice
Useful2 Signal2
Managed Settings

Gateway operators get startup errors for bad desktop policy keys instead of silently passing them through.

managed.policies
What

If 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.

Details
  • The previous build shallow-merged { match, cli, desktop } and served whatever was written.
  • Non-fatal findings, such as reports of dropped values and intake warnings, are logged as warnings and do not stop startup.
Evidence

desktop overlay invalid: refused or unparseable keys

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 →