claude-code - 💡(How to fix) Fix [BUG]  API Error: Stream idle timeout - partial response received - multiple time today [22 comments, 20 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46987Fetched 2026-04-13 05:44:29
View on GitHub
Comments
22
Participants
20
Timeline
32
Reactions
26

Error Message

API Error: Stream idle timeout - partial response received

Code Example

API Error: Stream idle timeout - partial response received
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Claude shows  API Error: Stream idle timeout - partial response received after stuck in between tool calls

What Should Happen?

Claude should create a .md file for a plan.

Error Messages/Logs

API Error: Stream idle timeout - partial response received

Steps to Reproduce

ask for a plan to implement a code. output a md plan

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.90

Claude Code Version

claude-code (2.1.92)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Downgrade to version 2.1.90 to potentially resolve the API Error: Stream idle timeout issue.

Guidance

  • Verify that the issue is indeed a regression by testing the same workflow in version 2.1.90 to confirm it works as expected.
  • Check the release notes for versions 2.1.91 and 2.1.92 to see if any changes related to API timeouts or streaming responses were introduced.
  • Test the current version (2.1.92) with a different model or a simpler request to isolate if the issue is specific to the Opus model or a more general problem.
  • Consider reaching out to the developers or checking the GitHub issues for any ongoing discussions or fixes related to this regression.

Example

No specific code example is applicable in this case, as the issue seems related to a version regression rather than a coding error.

Notes

The solution is based on the information provided that the issue is a regression and was working in version 2.1.90. Downgrading might not be a permanent solution but can help verify the cause.

Recommendation

Apply workaround: Downgrade to version 2.1.90, as it is confirmed to be working and can serve as a temporary solution until the regression is fixed in a newer version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING