Claude Code only processes one prompt per session, then times out until restart (WSL)

Status Fixed / completed
Maintainer reply None cached
Activity 12 comments · opened Apr 19, 2025 · closed May 8, 2025

Environment

  • Platform (select one):
  • [x ] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • Claude CLI version: 0.2.74 (Claude Code)
  • Operating System: Ubuntu 22.04.5 LTS (under Windows Subsystem for Linux)
  • Terminal: WSL

Bug Description

This started 2 days ago all of a sudden.
https://status.anthropic.com/ reports "All Systems Operational" during this whole time.
After starting Claude, I can send one prompt successfully. However, all subsequent prompts fail with a timeout error. The system enters a retry loop such as:

API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10)

Eventually, it fails entirely or says Claude is offline. Restarting the session allows one more prompt to go through before the issue occurs again.

Steps to Reproduce

  1. Start Claude CLI inside WSL.
  2. Send a prompt — works as expected.
  3. Send another prompt — fails with timeout.
  4. Restart Claude — issue resets and repeats.

Expected Behavior

Claude should continue to process multiple prompts in a session without timing out after the first one.

Actual Behavior

Only the first prompt works. Every subsequent prompt times out and enters a retry loop, making it unusable without restarting each time.

Additional Context

  • Consistently reproducible.
  • No network issues observed on the host system.
  • Running inside Windows 11 using WSL (Windows Subsystem for Linux).
  • Happy to provide logs or additional environment details if needed.

View original on GitHub ↗

12 Comments

dasrfp · 1 year ago

rampant speculation: possible interference from endpoint security software?

tomazbc · 1 year ago

Figured it out.
Addguard decided one day that https://statsig.anthropic.com/ should be blocked.
Allowing it fixed the issue.

jnz86 · 1 year ago

For me this was that my VPN was connected and AI companies hate VPNs.

vanman2024 · 1 year ago

I am getting this all time now its really annoying I don't use a VPN not sure what's causing it.

dylanh724 · 1 year ago

I'm getting it all the time with ExpressVPN. I often use a vpn so I'm not geodiscriminated, stereotyped or get tossed local websites in a 2nd language I'm not yet great at. Some sites also block external countries as if no one could possibly live abroad in 2025. Hence, a vpn.

Even if someone's using a vpn, they're spending tokens - please loosen the noose a bit folks. Actual bots that are being exploitive can surely be detected vs the average user with all this cutting-edge tech?

Heck, prompt a recaptcha - make ASCII art and ask us what it is. Anything but just a clearly-fake offline message that wastes our time and stops us from giving you money. Let us give you money.

@bcherny

ebibibi · 1 year ago

In my case, the fix was DNS-related. Here's what worked for me:

I added the following lines to /etc/wsl.conf:

[network]
generateResolvConf = false

Then I restarted the WSL environment completely (not just the shell).

Finally, I manually edited /etc/resolv.conf to specify a stable DNS server (e.g., 8.8.8.8).

After doing this, the problem disappeared — Claude Code now handles multiple prompts per session without timing out.

Hope this helps others still experiencing the issue!

Impulse354 · 1 year ago

@ebibibi
Thank you

burakgon · 1 year ago
Figured it out. Addguard decided one day that https://statsig.anthropic.com/ should be blocked. Allowing it fixed the issue.

Adding @@||https://statsig.anthropic.com^ to adguard home fixed the issue. Thank you!

nimlakasithum44-sudo · 1 year ago

[network]
generateResolvConf = false

nimlakasithum44-sudo · 1 year ago

API Error (Request timed out.) · Retrying in 1 seconds… (attempt 1/10)

nimlakasithum44-sudo · 1 year ago

Use10

github-actions[bot] · 1 year 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.