IDE integration issues on WSL

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

58 issues · 10 open · 48 resolved (83%) · first seen Feb 24, 2026

Is this getting better or worse?

This class of problem is converging. 17 new reports in the last 90 days vs 38 in the 90 before — -55%. The open backlog peaked at 19 in 2026-04 and sits at 10 today.

0 5 10 14 19 2026-022026-042026-062026-08
2026-02 — First reports2026-04 — Peak backlog (19 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

47 of these reports name the Claude Code build they were running, spanning 39 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 35 days across 48 closures. Of the 48 closures with a recorded reason, 17% were closed as completed and 40 as not-planned or duplicate. The most recent completed fix landed in 2026-06.

Workarounds reported by the community

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

[BUG] Extension: cannot set Effort = AUTO
Workaround: Edit and remove the entry
Found in the thread of #33011 · resolved
[BUG] AI-generated session titles override user renames and customTitle entries (v2.1.78+)
…verwrites (earlier report with full root cause analysis and workaround implementation) - 29801 — Titles differ between VS Code and Claude for Windows - 9898 — Poor session indexing design (auto-closed without fix) - 9668…
Found in the description of #36379 · resolved
[BUG] VS Code extension subprocess init timeout on WSL2/Ubuntu 26.04 — CLI fully healthy (stream-json handshake works from terminal)
…ot the binary. claudeCode.useTerminal mode works flawlessly as a workaround. What Should Happen? The VS Code extension should connect to Claude and become ready within a few seconds, like the CLI does. Error Messages/Log…
Found in the description of #64168 · resolved
[BUG] claudeCode.environmentVariables are not applied in WSL (Remote) environment
…o use the extension. Result: Connection fails / Timeout. 5. Workaround: Open the integrated WSL terminal and run: export ANTHROPIC BASE URL=" export ANTHROPIC API KEY="xx-xxx-..." 6. Attempt to use the extension again. R…
Found in the description of #37709 · resolved
[BUG] Selection context ("N lines selected") not shown for gitignored files in VSCode extension
…rsion Unknown — may never have worked for gitignored files. Workaround None known short of temporarily removing the file from . Related Issues - 8451 (missing ide selection on Linux/WSL2) - 14153 (selection context not p…
Found in the description of #29433 · resolved

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–58

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. IDE integration issues on VS Code

    1,307 issues
  2. IDE integration issues on Windows

    869 issues
  3. IDE integration issues on macOS

    828 issues
  4. IDE integration issues on Linux

    274 issues
  5. Terminal UI issues on WSL

    155 issues
  6. Core CLI issues on WSL

    83 issues
  7. Model behaviour issues on WSL

    79 issues
  8. Agents issues on WSL

    67 issues