claude-code - 💡(How to fix) Fix constant API errors and Opus 4.7 (1M) keeps switching to Opus 4.7 - running on edge [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#53341Fetched 2026-04-26 05:18:15
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
0
Timeline (top)
labeled ×6commented ×1cross-referenced ×1subscribed ×1

Error Message

API Error: Stream idle timeout - partial response received

Turn failed Try sending it again

Code Example

API Error: Stream idle timeout - partial response received

Turn failed
Try sending it again
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?

I keep getting the "API Error: Stream idle timeout - partial response received

Turn failed Try sending it again"

and at the same time I start the session with Opus 4.7 (1m) and it just switches to regular Opus 4.7

What Should Happen?

it should not give me this API error and definitely when the model is chosen should not switch unless I switch it. This was on the edge browser, I don't seem to be having these issues in Chorme

Error Messages/Logs

API Error: Stream idle timeout - partial response received

Turn failed
Try sending it again

Steps to Reproduce

sending any complex request

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

not sure but before this latest big UI/UX change a few days ago.

Claude Code Version

not sure, I ask and claude just says Opus 4.7

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by trying a different browser or checking the network connection to rule out any issues with the Edge browser.

Guidance

  • Try reproducing the issue in another browser, such as Chrome, to see if the problem is browser-specific.
  • Check the network connection to ensure it is stable and not causing the "Stream idle timeout" error.
  • Verify that the issue persists when sending simple requests to isolate if the problem is specific to complex requests.
  • Consider reaching out to the Anthropic API support for further assistance, as the issue may be related to their service.

Notes

The exact cause of the issue is unclear, and more information about the network setup and the specific requests being sent would be helpful in diagnosing the problem.

Recommendation

Apply workaround: Try using a different browser or checking the network connection, as this may resolve or provide more insight into the issue.

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

claude-code - 💡(How to fix) Fix constant API errors and Opus 4.7 (1M) keeps switching to Opus 4.7 - running on edge [1 comments, 2 participants]