claude-code - 💡(How to fix) Fix [BUG] Rate limit error (429) triggers unexpected plan usage consumption in Claude Code (Windows)

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…

Error Message

When Claude Code shows the error “API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited”, a large chunk of my plan usage is consumed even though I’m not actively using Claude and nothing is running in the background. This has happened repeatedly today, wasting hours of usage and blocking work. The rate limit message is separate from my plan usage limit, but the two are being linked incorrectly in practice.

Error Messages/Logs

Wait for the “Rate limited” banner to appear (all the chats will immediately stop and show the rate error). Actual: Rate limit error correlates with large usage increases, suggesting a bug where rate limiting is being treated like usage.

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?

When Claude Code shows the error “API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited”, a large chunk of my plan usage is consumed even though I’m not actively using Claude and nothing is running in the background. This has happened repeatedly today, wasting hours of usage and blocking work. The rate limit message is separate from my plan usage limit, but the two are being linked incorrectly in practice.

<img width="1326" height="536" alt="Image" src="https://github.com/user-attachments/assets/02ad1286-bab4-4701-90ff-672b428cf17d" /> <img width="1747" height="671" alt="Image" src="https://github.com/user-attachments/assets/4bd8dca7-677b-466c-9d31-491c44fcb17a" />

What Should Happen?

This bug should be fixed and users experiencing this should be refunded their lost usage.

Error Messages/Logs

Steps to Reproduce

Plan: Max 20x Open Claude Code (Windows) run around 3 chat sessions with Opus 4.7 Max and leave it for a few seconds. Wait for the “Rate limited” banner to appear (all the chats will immediately stop and show the rate error). Check Settings → Usage immediately after: session and weekly usage jump significantly (e.g., ~26% session) even with minimal or no interaction. Expected: Rate limiting should not consume plan usage unless actual tokens are used. Actual: Rate limit error correlates with large usage increases, suggesting a bug where rate limiting is being treated like usage.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.71

Claude Code Version

1.35 Windows App

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by downgrading to version 2.1.71 of Claude Code, where the rate limiting bug was not present.

Guidance

  • Verify that the issue is indeed caused by the rate limiting mechanism by checking the usage before and after the "Rate limited" banner appears.
  • Try to reproduce the issue with a minimal number of chat sessions to see if the usage increase is consistent.
  • Check the Anthropic API documentation to see if there are any known issues or workarounds related to rate limiting.
  • Consider reaching out to the Anthropic API support team to report the issue and ask for assistance.

Example

No code snippet is provided as the issue seems to be related to the Claude Code application and the Anthropic API, and no specific code is mentioned.

Notes

The issue seems to be a regression, as it worked in a previous version (2.1.71) of Claude Code. The exact cause of the issue is not clear, but downgrading to the previous version may provide a temporary workaround.

Recommendation

Apply workaround: Downgrade to version 2.1.71 of Claude Code, as it is the last known working version. This should prevent the unnecessary consumption of plan usage due to the rate limiting bug.

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