{"version":"2.1.269","anchor":"wsl-managed-settings-warnings-can-now-be-tagged-wslignored","canonical_anchor":"wsl-managed-settings-warnings-can-now-be-tagged-wslignored","heading":"WSL managed-settings warnings can now be tagged wslIgnored","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/wsl-managed-settings-warnings-can-now-be-tagged-wslignored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### WSL managed-settings warnings can now be tagged wslIgnored\n\nWSL managed-settings warnings can now be flagged as ignored instead of just being dropped\n\n**Unclear.** What consumes the `wslIgnored` flag or how it's surfaced to a user is not shown by the finding.\n\n**What**\n\nOn Windows Subsystem for Linux (WSL), certain managed settings are not read from the Windows registry (HKCU). When Claude Code resolves managed configuration in this situation, warning-level errors that previously would have been dropped are now instead kept and marked with a new `wslIgnored` flag.\n\n**Why**\n\nKeeping these warnings instead of silently discarding them means the information about what was ignored on WSL is preserved and can be surfaced or inspected, rather than disappearing.\n\n- Area: Elsewhere\n- Names: `wslIgnored`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}