What
Managed settings are the settings an organization pushes to its users. How Claude Code handles invalid values in them has been reworked:
- Keys such as
allowManagedHooksOnly,syncClaudeAiSkills,remoteToolsanddisableSideloadFlagsno longer each have their own fallback. One shared rule now treats any invalid value as that key's restrictive value and says so in a warning. - A true or false written in quotes, such as "true", is now read as the true or false value, with a warning.
- A key that can only switch something off, set to false, is treated as if it were not there.
- Each
enabledPluginsentry is now checked on its own. An invalid entry is dropped and that plugin is neither forced on nor blocked, instead of the whole list being thrown away. strictPluginOnlyCustomizationnow warns about names in it that it does not recognise.- A new warning appears when the only policy content from a source is these strict fallback values.
Why
A single typo in one plugin entry no longer throws away the whole plugin policy, and quoted true and false values, which some device management tools produce, now work.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not confirmed that every key's new restrictive fallback matches the one it used before.