1 person reported

All time, since Sep 29.

Request hangs after network change

“After the laptop switches to a different Wi-Fi network, the next prompt gets no response for about 3 minutes.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/794/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Next request hangs about 3 minutes after network change. After switching Wi-Fi or subnet, Claude Code waits 180 to 184 s for response headers on a dead connection, then retry succeeds.

Is this your bug?

File my report
Where
API client
Error text
No response from the API after 3m · retrying once, waiting up to 10m
Versions
2.1.284 to 2.1.289
Platforms
Linux
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Session hangs on stalled stream2 people

Original reports2, newest first

  1. After a network change, the next request hangs 180s on a dead connection before retrying (Linux)#99524
  2. After a Wi-Fi change, the next request hangs 184 s on a dead connection before retrying (Linux)#98184

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.