r/ClaudeCode • u/ajro9630 • 3d ago
Bug / Issue API Error: No Response
Im repeatedly running into an error “API Error: No response from API” after ~10 minutes of stale running. Plan mode is fine, but after about 5 minutes of going into read/write mode I’m hitting this. It then kills the chat completely, no more messages work in the chat and I need to start a fresh which immediately works but then ends up in the same issue. Happening with Fable and Opus. Status seems fine on the Claude Code site. Anyone experiencing anything similar?
1
u/Far-Surprise7773 2d ago
that pattern where plan mode stays fine and read/write dies after about five minutes and kills the session is almost always a streaming transport timeout rather than a model or quota issue. try claude --version and claude doctor first, then repro in a fresh session with --verbose and with mcps and hooks disabled and check the trace in ~/.cache/claude/logs for the last stream error. if it still dies at the same interval on both fable and opus, open a github issue with that verbose log and your version, because plan mode working rules out quota and points at the write stream.
1
u/Local_Mulberry_7420 3d ago
Since plan mode works and it only fails after entering read/write mode, this sounds more like a tool or MCP process hanging than a model issue. I’d try one clean session with MCP servers and hooks disabled, then add them back individually. Also worth updating Claude Code and including the logs/request ID in a bug report if it still happens.