The desktop app issues on WSL

Issues the maintainers labelled both platform:wsl and area:desktop.

51 issues · 29 open · 22 resolved (43%) · first seen Mar 21, 2026

Is this getting better or worse?

This class of problem is still growing. 31 new reports in the last 90 days vs 11 in the 90 before — +182%. The open backlog peaked at 29 in 2026-10 and sits at 29 today.

0 7 15 22 29 2026-032026-052026-082026-10
2026-03 — First reports2026-08 — Most new reports (14)2026-10 — Peak backlog (29 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

26 of these reports name the Claude Code build they were running, spanning 19 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 34 days across 22 closures. Of the 22 closures with a recorded reason, 36% were closed as completed and 14 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

17 of these issues post a workaround someone says worked. The highest-engagement ones:

[Feature Request] Native WSL Remote Integration for Claude Code Desktop on Windows
…l: wrong shell, broken paths, toolchain mismatches. The SSH workaround is too clunky for daily use. VS Code's Remote - WSL solved this years ago. Claude Code Desktop deserves the same. This would unlock the Desktop UI fo…
Found in the thread of #49933 · resolved
New session always opens in last used project directory instead of selected one
…han the last used project from the desktop app UI. The only workaround is to run from the terminal inside the target directory.
Found in the description of #49888 · resolved
[BUG] Claude Code desktop ignores permission configurations for WSL projects, requiring approval for every file operation despite proper settings
…s correctly, so glob patterns in settings.json never match. Workaround — use CLI instead of Desktop: The CLI version runs natively in WSL and resolves paths correctly. Permission settings in (WSL-side) work as expected.…
Found in the thread of #37192 · resolved
WSL-path folder selection forces "WSL" environment instead of "Local", breaking Chrome extension and MCP plugins (regression)
…vironment to WSL, with no way to keep it Local. I tried two workarounds and both still flip to WSL: - explicitly choosing "Local" in the environment picker before selecting the folder; - mapping the \\wsl.localhost path…
Found in the thread of #77788 · still open
Desktop app file viewer cannot open links to files under additionalDirectories
+1 for me. There is a manual workaround, but it is a pain to do it in every session. I haven't found a way to make it happen automatically. Here's how Claude describes the workaround: Workaround: ask Claude to explicitly…
Found in the thread of #94446 · still open

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–51

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. The desktop app issues on macOS

    2,253 issues
  2. The desktop app issues on Windows

    2,230 issues
  3. The desktop app issues on Linux

    167 issues
  4. Terminal UI issues on WSL

    181 issues
  5. Core CLI issues on WSL

    101 issues
  6. Model behaviour issues on WSL

    91 issues
  7. Agents issues on WSL

    83 issues
  8. IDE integration issues on WSL

    82 issues