{"version":"2.1.118","anchor":"wsl-managed-settings-inheritance","canonical_anchor":"wsl-managed-settings-inheritance","heading":"WSL Managed Settings Inheritance","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.118\/e\/wsl-managed-settings-inheritance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.118","markdown":"### WSL Managed Settings Inheritance\n\n**What**\n\nWSL (Windows Subsystem for Linux) instances can now inherit managed settings from the Windows host's policy chain.\n\n**Details**\n\n- A new `wslInheritsWindowsSettings` boolean setting controls this behavior\n- When set to `true` in a Windows admin-only source (HKLM registry or `C:\/Program Files\/ClaudeCode\/managed-settings.json`), WSL reads managed settings from the full Windows policy chain\n- Windows sources take priority over Linux-native `\/etc\/claude-code` settings\n- Double opt-in required: admin enables the chain via HKLM\/HKCU, user confirms via their own HKCU entry\n- Uses `reg.exe` queries via `\/mnt\/c\/Windows\/System32\/reg.exe` for cross-environment access\n- Drop-in settings from `C:\/Program Files\/ClaudeCode\/managed-settings.d\/` are also supported\n\n**Evidence**\n\nSchema description (search for `\"wslInheritsWindowsSettings\"`) and WSL detection function `pnH()` at line ~50906."}