[BUG] API Error: Rate Limit when using claude code (vscode) on max plan

Resolved 💬 21 comments Opened Mar 11, 2026 by csidi90 Closed Mar 17, 2026
💡 Likely answer: A maintainer (hackyon-anthropic, collaborator) responded on this thread — see the highlighted reply below.

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?

I am using claude code (vscode extension) for a long time now and recently updated the extension to the latest version. Eversince then, it is using opus 4.6 for my workloada nd I keep receiving "API Error rate limit reached" messages. I am nowhere near any limitations and before I have never once experienced this issue with my workload.

I am paying 100€ a month for the max subscription, the claude.ai usage shows barely any usage so why am I keep receiving this?

I was a happy paying customer that produced several thousand USD revenue for anthropic already, but this is unaacceptable for me.

<img width="967" height="395" alt="Image" src="https://github.com/user-attachments/assets/038e39ef-0929-4165-94e8-0158c1669d67" />

What Should Happen?

No API rate limit reached error messages

Error Messages/Logs

api error rate limit reached

Steps to Reproduce

Just type anything and randomly receive that error

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.71

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

21 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/29579
  2. https://github.com/anthropics/claude-code/issues/30723
  3. https://github.com/anthropics/claude-code/issues/32536

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

laniakea001 · 4 months ago

Sorry to hear about this frustrating experience — being rate-limited despite being on the max plan is definitely unacceptable.

A few things that might help in the meantime:

  1. Check VS Code extension vs Claude Code CLI: The rate limits may be separate. Try using the CLI directly (claude) instead of the VS Code extension to see if the issue persists.
  1. API key vs Anthropic account: If you're using an API key directly (vs. authenticated via anthropic.ai), check if there's a separate rate limit on that key at the Anthropic console.
  1. Token usage monitoring: Sometimes high token usage triggers limits. Check your console for detailed usage.

For a more robust solution, you might want to look into agent frameworks with local processing (like OpenClaw) that can run autonomously without hitting API rate limits for routine operations — they only call the LLM when needed, reducing overall API consumption.

Would be happy to help debug further if you share more details about your setup!

jordan-jarolim · 4 months ago

I have the same problem with the VScode extension since yesterday. I tried 2 different machines, tried logging in with the Claude MAX subscription as well as the API key, ran in empty folder, restarted and reinstalled multiple times and still get the same error. Everything works in terminal and desktop.

gabriel-vthereagency · 4 months ago

The error message is misleading. In my case, “API Error: Rate limit reached” was triggered because the VS Code chat had switched to a 1M context model that is not included in my Pro plan. This was not a real rate limit issue. The message should clearly indicate that the selected model is unavailable for the current plan, instead of suggesting usage exhaustion.

ljbade · 4 months ago

I got same problem today, didn't have this issue a few days ago. The Windows Claude app on code tab works fine though, so its a bug specific to VSCode,

ljbade · 4 months ago

@gabriel-vthereagency thats genious, I simple went to the VSCode extension model select menu, hit just "Sonnet 4.6" and now it works!

So the bug seems to be related to having an invalid model selected somehow, and then the rate limit error is misleading.

It should say "Invalid model for your plan" or something to prompt people to try switching models to fix.

Imjoe418 · 4 months ago

Same issue here. Pro plan, Windows 11, Cursor (VS Code fork), latest Claude Code extension.

Opus 4.6 instantly returns "API Error: Rate limit reached" on any message, even a simple "hello". Sonnet works fine in the same extension. Opus also works perfectly in Claude Desktop (Code tab) and on claude.ai — so the issue is specifically with the VS Code extension + Opus.

My usage is at 5% session / 14% weekly, nowhere near any limit.

I've tried everything:

  • Full uninstall of the extension
  • Deleted %USERPROFILE%\.claude folder
  • Fresh reinstall + re-login with Claude.ai Subscription
  • No ANTHROPIC_API_KEY set
  • Set CLAUDE_CODE_DISABLE_1M_CONTEXT=true (no effect on the extension)
  • Contacted support — they said all incidents were resolved and it was on my end, but nothing fixed it

Also noticed the Account & Usage panel shows "Plan: Claude api" instead of "Pro", which seems wrong.

It's been a week since this issue was opened. @csidi90 is it still happening for you?

See also #30824 and #33154 — same pattern. This needs attention, paying subscribers can't use Opus through the extension.

dabadema · 4 months ago

Really looking forward to hearing news from this issue.

I am at same point than most of people here....

Imjoe418 · 4 months ago

Fix: In VS Code/Cursor, go to Extensions → Claude Code → click the dropdown arrow next to Uninstall → "Install Another Version" → select v2.1.72. Disable auto-update to prevent it from updating back.

dabadema · 4 months ago
Fix: In VS Code/Cursor, go to Extensions → Claude Code → click the dropdown arrow next to Uninstall → "Install Another Version" → select v2.1.72. Disable auto-update to prevent it from updating back.

Thanks a lot buddy! it’s working perfectly with that temporary solution, think that Claude should fix that soon…

hackyon-anthropic collaborator · 4 months ago

We're coming up with a fix! Please use /model to select the opus model if you see this again

Mruchniak · 4 months ago

You need to put CLAUDE_CODE_DISABLE_1M_CONTEXT=1 in env variables for opus.

You can switch to sonnet via CLI /model and ask it to change that for OPUS settings and you're good to go.

younesriouche-sudo · 3 months ago

same issue here, I just changed the model to Haiku then to Sonnet and it workssss :)

kaushal8111 · 3 months ago

Switching to v2.1.72 did not help. Any other thought?
Also, tried selecting specific model, still keep getting the error.

On checking usage ? - a lot reamining.

paulinventome · 3 months ago

I am seeing the same thing in VS Code. Switch models away from [1m[ appears to have solved it but that's hardly the point. I'm on Max x5 at the moment, I've reauthenticated and the context shows 1m but get API rate error trying anything.

jdpierce21 · 3 months ago

I was having the issue, but I updated to v2.1.81, and it seems to have fixed it (at least for now).

iliagerash · 3 months ago

I downgraded from 2.1.81 to 2.1.79 and it helped. Never used Opus, API rate limit happened with Sonnet

jdpierce21 · 3 months ago
I was having the issue, but I updated to v2.1.81, and it seems to have fixed it (at least for now).

Update: the issue is back. Toggling between opus 200k and opus 1m fixes the issue.

kaushal8111 · 3 months ago

the issue is back. Toggling between opus 200k and opus 1m fixes the issue. --- How to do this?

Also, in VS Code extension do we need some more access/billing? I have the pro version.

Mika255 · 3 months ago

Downgraded to vscode extension 2.1.81 fixed it.
Still selected Opus as model

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.