[BUG] Waiting for API response every reply

Yes, since now (2027-10-11 5p.m.) in 1 PHPStorm (Claude Code Session), every prompt returns "Waiting for API response · will retry in 2m 33s · check your network, after that "API Error: Response stalled mid-stream. The response above may be incomplete.".... unable to work!

Windows 11 25H2
Claude Code 2.1.207
PHPStorm 2026.1

The Prompt (in German), which NOT worked ...is there any security related words or data inside?!?

Kontext:
Du arbeitest in einer modernen Laravel 13 Codebase mit Filament v5, Livewire 4 und PHP 8.5, PostgrSQL mit pgvector extension.
Das Projekt folgt Clean Architecture Prinzipien, S.O.L.I.D.- und DRY-Prinzip, sowie PSR-Standards und wird umfassend mit Pest getestet.

Input:
Lies und analysiere die Spezifikation genau und detailliert:
"F:\__ServBay\www\download-radar.demo\docs\superpowers\specs\2026-07-09-undo-redo-feed-item-triage-design.md"

Ziel:
Erstelle einen detaillierten, direkt umsetzbaren Entwicklungsplan basierend auf dieser Spezifikation.

Anforderungen an den Plan:
- Unterteile den Plan in sinnvolle Phasen (z. B. Domain, Datenbank, Backend, UI, Testing)
- Beschreibe konkrete Implementierungsschritte (keine rein abstrakten Beschreibungen)
- Nutze die aktuellesten Laravel(v13.x)-spezifische und neueste PHP 8.5 Lösungen (Eloquent Modelle, Services, Actions, Policies, etc.)
- Berücksichtige die Struktur von Filament Ressourcen und Pages, falls relevant
- Definiere die notwengigen Datenbankschemata-Änderugnen (Tabellen, Beziehungen, sinnvolle Indizes)
- Identifiziere Edge Cases und potenzielle Risiken
- Definiere eine Testing-Strategie (Pest) -> TDD
- Schlage sinnvolle Datei- und Klassenstrukturen vor, wo hilfreich

Output-Format:
- Klare Abschnitte pro Phase
- Schritt-für-Schritt Aufgaben (actionable)
- Präzise und kompakt, kein unnötiger Text

Constraints:
- Bevorzuge einfache Lösungen gegenüber Overengineering
- Halte dich strikt an Laravel- und Filament-Konventionen (neuste Versionen; Laravel 13.x , Filament v5.x)
- Vermeide unnötige Abstraktionen, außer sie sind klar begründet
- Gehe von produktionsreifer Codequalität aus

Optional:
- Füge einen Abschnitt „Offene Fragen“ hinzu, falls die Spezifikation unklar ist
- Füge „Nice-to-have Verbesserungen“ hinzu, klar getrennt vom Kernplan

Wenn Du Ungereimtheiten feststellsst, dann zeige sie mir, mit Lösungsmöglichkeiten und einer klaren Empfehlung von dir.

Starte jetzt.

Update (2026-07-11 18:18):
Claude Code seems inconsistent compared to Claude Cowork. I was able to create a plan (with the exact same prompt) successfully using Claude Cowork (with access to the project folder), and it worked perfectly. However, Claude Code does not seem to handle the same task correctly or produce the expected result.

Update (2026-07-23 16:56):
Is seems, that Anthropic has changed something, because, my big/huge specs (from superpowers) could be now transformed into a Plan (superpowerswroting-plans); without "Waiting for API Response" or complete fail. HTX

this is happening quite often for me as well

I don't get it every response, but it happens very regularly, even in 2.1.212

+1, I don't know if its a server issue upstream or the claude code client itself but it seems to happen frequently.

Happens a lot for me still.

Happens also for me when using a local model via unsloth start claude. The average latency (i.e. the time before the model even starts processing) is ~100s.

我也遇到了类似情况，请问现在有解决方法吗？

this happens a lot for me too

this is happening to me pretty often. Any way to avoid it?

Yep I'm getting the same thing in Claude on my ASUS GX10 running VLLM connected to Claude. Open WebUI and Open Code have no issues. It seems to be a Claude Code CLI issue

To prevent auto-closing this issue as "stale": this bug is still present on 2.1.274.

never had this issue, started to appear since yesterday

Been like this all week. When I finally realize it's stuck, pressing escape and re-prompting with "continue" makes it go again, but it's pretty frustrating having to babysit it.

Steps to Reproduce Use claude code

😂😂This is the best line ever recorded on GitHub... love that.

And yes, I now am getting Waiting for API response almost every request lately (yesterday and today 10/5/2026)...

Happening for me to constantly - started a few days ago.

Just starting happening quite often for me today. I'm using Claude Code in a terminal with vscode.

When using Warp Terminal exsiting!!!!!

This is occurring for me on every response in my Windows terminal but not on Mac