Gateway operators get startup errors for bad desktop policy keys instead of silently passing them through.
What's wrong with this entry?
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.
- 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.
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.
-
v2.1.228
Managed settings accept per-OS
policyHelpersBoth mention managed policy
-
v2.1.228
New
policyHelpersmanaged-settings key for per-OS policy helper executablesBoth mention managed policy
-
v2.1.235
Policy helpers can be delivered by remote managed settings, after explicit approval
Both mention managed policy