{"version":"2.1.302","anchor":"wsl-detection-changed","canonical_anchor":"wsl-detection-changed","heading":"WSL detection no longer relies on WSL_DISTRO_NAME alone","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/wsl-detection-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### WSL detection no longer relies on `WSL_DISTRO_NAME` alone\n\nClaude Code no longer always treats `WSL_DISTRO_NAME` being set as proof it runs under WSL, and can fall back to checking the system\n\n**Unclear.** It is not clear what condition decides whether `WSL_DISTRO_NAME` is still trusted.\n\n**What**\n\nWSL (Windows Subsystem for Linux) lets you run Linux inside Windows, and Claude Code adjusts some behaviour when it runs there. Before, having the `WSL_DISTRO_NAME` environment variable set was always enough for Claude Code to decide it was under WSL. Now it runs another check first, and only trusts that variable when that check does not hold. Otherwise it looks at the system's version information instead.\n\n**Why**\n\nIf you run Claude Code in a container or another setup where `WSL_DISTRO_NAME` is set but you are not really under WSL, it may now be detected correctly.\n\n- Area: Elsewhere\n- Names: `WSL_DISTRO_NAME`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}