Agents issues on WSL

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

67 issues · 15 open · 52 resolved (78%) · first seen Mar 4, 2026

Is this getting better or worse?

This class of problem is holding steady. 35 new reports in the last 90 days vs 32 in the 90 before — +9%. The open backlog peaked at 16 in 2026-07 and sits at 15 today.

0 4 8 12 16 2026-032026-042026-052026-062026-072026-08
2026-03 — First reports2026-06 — Most new reports (16)2026-07 — Peak backlog (16 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

49 of these reports name the Claude Code build they were running, spanning 37 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 52 closures. Of the 52 closures with a recorded reason, 23% were closed as completed and 40 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

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

[BUG] Agent tool isolation: "worktree" has no effect for team agents — agent runs in main repo
…rktree so the agent works on an isolated copy of the repo." As a workaround, we manually create git worktrees before spawning agents: ...and set in the agent prompt to the worktree path. This works correctly, but the par…
Found in the description of #33045 · resolved
[BUG] Agent Teams: Single teammate spawn creates 10-151 duplicate worker instances, each consuming full context and actively editing files
…by at least one round-trip latency, not zero. One practical workaround we've been using in an out-of-process coordinator context (external process that calls per agent, tracks subagent files, and refuses to re-spawn if a…
Found in the thread of #55586 · resolved
[BUG] SendMessage silently fails when using agent name — only agent ID works for resuming completed agents
…schema (using names as documented) consistently fail - The workaround (using agent IDs) contradicts the tool's own documentation - In multi-agent pipelines, this causes wasted agent spawns and redundant work Workaround…
Found in the description of #42999 · resolved
Background subagents do not inherit Write/Edit permission allow rules from settings.json or settings.local.json
…main-session takeover or foreground subagent fallback. The workaround "run it in foreground" was not discoverable without controlled testing. Ask Either (a) fix propagation so background subagents honor allow rules, or…
Found in the description of #67906 · resolved
[BUG] Agent tool `model` parameter enum rejects 1M-context variants (`opus[1m]`, `claude-opus-4-7[1m]`)
…ot target it from code. This forces a global settings-level workaround that cannot differ between subagents in the same session (e.g. a persistent Architect needing 1M, while a short-lived one-shot Defect-Fixer is fine w…
Found in the description of #51254 · 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–67

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. Agents issues on macOS

    880 issues
  2. Agents issues on Windows

    356 issues
  3. Agents issues on Linux

    257 issues
  4. Agents issues on VS Code

    70 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. IDE integration issues on WSL

    58 issues