[BUG] Rate limit error (429) triggers unexpected plan usage consumption in Claude Code (Windows)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] 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_