[BUG] Extremely slow thinking/response time on WSL2 - works fine on native Linux

Status Closed — not planned
Reported on v2.1.17
Maintainer reply None cached
Activity 9 comments · opened Feb 3, 2026 · closed Apr 8, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

Every prompt takes an abnormally long thinking/response time on WSL2. This happens consistently on every single prompt, regardless of complexity or token count. The same account on native Ubuntu Linux responds within seconds.

Important finding: The stable version (2.1.17) runs perfectly fine on the same WSL2 setup. The issue only occurs on the latest channel (2.1.29+). This strongly suggests a regression introduced after 2.1.17.

Observed timing examples (Opus 4.5, latest channel v2.1.29):

| Prompt complexity | Output tokens (approx.) | Thinking time |
|---|---|---|
| Simple question | ~745 | 1m 27s |
| Short code explanation | ~1,000 | ~4m 00s |
| One-liner fix | ~500 | ~1m 50s |
| Medium code review | ~2,200 | ~6m 10s |
| Short config question | ~300 | ~1m 15s |
| File read + small edit | ~1,800 | ~3m 40s |
| Multi-step task | ~2,500 | ~5m 20s |
| Simple greeting/hello | ~200 | ~1m 05s |
| Bug analysis | ~1,500 | ~2m 55s |
| Refactoring suggestion | ~2,000 | ~4m 30s |

On native Ubuntu Linux with the same account: all of these complete in seconds, not minutes.
On WSL2 with stable version 2.1.17: also fast, no issues.

What Should Happen?

Thinking/response time should be comparable to native Linux and to stable version 2.1.17 (seconds, not minutes).

Steps to Reproduce

  1. Install Claude Code latest channel on WSL2 (Ubuntu 24.04 on Windows 11)
  2. Open any project (or no project at all)
  3. Send any prompt - even "hello"
  4. Observe thinking time of ~1-6 minutes before response begins
  5. Compare: switch to stable version 2.1.17 on the same WSL2 → completes in seconds
  6. Compare: run the same prompt on native Linux with the same account → completes in seconds

Troubleshooting Already Attempted

  • Completely uninstalled Claude Code (deleted all config/cache/data)
  • Fresh install following official documentation
  • Tested stable version 2.1.17 → works perfectly fine on WSL2
  • Switched to native Ubuntu Linux to rule out account-level throttling → works perfectly fine
  • Windows 11, WSL2, Node.js, npm, pnpm all on latest versions

Is this a regression?

Yes. Stable version 2.1.17 works correctly on WSL2. The issue is specific to the latest channel.

Last Working Version

Stable 2.1.17 works fine. Issue started around January 23, 2026 on the latest channel and has persisted through every update since.

Claude Code Version

2.1.29 (latest channel - broken)
2.1.17 (stable channel - works fine)

Platform

Anthropic API (Claude Max subscription)

Operating System

Windows 11 + WSL2 (Ubuntu 24.04.3 LTS, kernel 6.6.87.2-microsoft-standard-WSL2)

Terminal/Shell

VS Code integrated terminal (VS Code extension v2.1.29)

Additional Information

  • Model: Opus 4.5 (default)
  • Node: v24.13.0
  • npm: 11.7.0
  • pnpm: 10.28.2
  • Login: Claude Max Account

This is WSL2 + latest-channel specific. The exact same WSL2 environment with stable 2.1.17 works fine. Native Ubuntu Linux also works fine. The slowness is exclusively in the "thinking" phase, not in streaming the output.

View original on GitHub ↗

9 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/16429
  2. https://github.com/anthropics/claude-code/issues/17330
  3. https://github.com/anthropics/claude-code/issues/22497

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

shimscho · 6 months ago

… (4m 40s · ↑ 0 tokens) naaah.. its complete broken

DonRedwoood · 6 months ago

I'm baffled that this has been happening for several weeks on WSL2 and none of the bug reports have gotten any serious attention from Anthropic. This is literally 40-50% of all Windows devs.

yousecjoe · 6 months ago
I'm baffled that this has been happening for several weeks on WSL2 and none of the bug reports have gotten any serious attention from Anthropic. This is literally 40-50% of all Windows devs.

Agreed. Same boat here, still today, Thu Feb 19, Claude Opus 4.6 takes >30 minutes to "think" and the response it does give is useless. It's like it has been to Mars and got the lobotomy. It's eating through usage in the sloppiest and most inefficient manner. It takes an entire context window to read files that are <400 lines of code. I am watching it now going on >40 minutes "thinking" and trying to carry 166k tokens through compaction.

schugazi · 5 months ago

Still seeing this on 2.1.71

shimscho · 5 months ago

it's got worse

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

DonRedwoood · 4 months ago

Pathetic. This is still a massive issue. Automatic issue closing for a definite major bug is exceedingly ironic for a company bragging about their engineering team not having to hand-type code anymore. What? Did your team burn through their token allotment?

github-actions[bot] · 4 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.