wslInheritsWindowsSettings and managedSourcesBehavior appear in a key list with no visible consumer.
A list of settings keys now names managedSourcesBehavior and wslInheritsWindowsSettings, suggesting Windows settings can be inherited into WSL and that managed sources have configurable behaviour. What consumes the list, whether merge policy, migration or display, is not determined by the list itself. A separate list names enabledPlugins and extraKnownMarketplaces.
["managedSourcesBehavior", "wslInheritsWindowsSettings"]
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| [`wslInheritsWindowsSettings`](/docs/en/settings-reference#wslinheritswindowssettings) | When set in the HKLM registry or a file under `C:\Program Files\ClaudeCode`, have WSL read the Windows policy chain, and read `/etc/claude-code` onl…managed-settings see the edit
The hooks lock and `allowManagedPermissionRulesOnly`'s effect on the developer's own rules need the winning source by default; under the `managedSourcesBehavior` merge opt-in in [how Claude Code combines managed sources](/docs/en/managed-s…claude-apps-gateway see the edit
Choose whether Claude Code applies only the highest-priority [managed source](/docs/en/managed-settings#how-claude-code-combines-managed-sources) your organization delivers, or combines every admin source it delivers. By default Claude Cod…settings-reference see the edit
* **Gateway sign-in keys**: Claude Code never reads [`forceLoginGatewayUrl`](/docs/en/settings-reference#forcelogingatewayurl) or the `"gateway"` value of [`forceLoginMethod`](/docs/en/settings-reference#forceloginmethod) from server-manag…server-managed-settings see the edit
A small documentation edit on Configure server-managed settings touched a line naming managedSourcesBehavior after this was published.