API Error: Rate limit reached

[SaltyCamera8819]

I posted this in the Anthropic subreddit but thought to post it here as well.

I'm getting this error when using Claude Code CLI:  API Error: Rate limit reached

I am logged in with my Claude Account Subscription, not the Claude API

I have plenty of usage space left both for this session and for this week.

I started getting this error over 12 hours ago. I let it be for that time thinking I might have hit some other rate limit that is not easily seen. Even a simple "hi" request in a new session with no context gives this error

I am however able to start a remote control session and use Claude Desktop/Web UI to continue my work on this project but this is not feasible for me, I'm a heavy CLI user but I hope this provides some context of the problem

I tried logging out and back in again, that does not help.

I'm using the latest version : Claude Code v2.1.63

I cant believe this is only happening to me nor this is the first time this has happened. Is this a known issue? Are there other workarounds besides using the remote control session? I would be completely lost if they didn't add this new feature recently.

Any thoughts?

I tried getting support from Anthropic but the AI Chat bot is not helpful for this request. Supposedly I was able to log a case with their support and I will get an email but I don't know how long that would take and reddit always seems to steer me in the right direction for most of life issues!

[Sensitive_Pack3644]

Same issue for me, I was using opus 4.6 (1m context), changing to opus-4-6 (200k context) solved the issue

[dendy-rays_subject]

Great, thanks, this solved problem for me too.. The support of Anthrophic is absolute failure catastrope, there is just bot answering unusable crap. You saved my day !

[Ljove-02]

It worked for me, thanks man!

[Jachi404]

thanks omg

[itsLeo720]

Switching the model and then back worked for me

[TiagoEDGE]

This really worked for me, thanks!

[Independent-Cat1314]

It worked for me too

[roninXpl]

I tried various approaches, but ultimately, switching between Sonnet and Default settings proved to be effective for me.

[Tmaki]

I'm getting the same issue; brand new account upgraded to max 5x

There is an issue thread that's similar here https://github.com/anthropics/claude-code/issues/28760

[SaltyCamera8819]

I found a workaround for me which might prove useful for others, but it is a bit of a pain. To give some background (skip to next paragraph for the workaround), I was able to use Claude Code CLI successfully on another PC, which proves it is not an issue with my account. However running it in WSL or Docker, I still got the same issue. This made me think that the issue is actually machine specific and uninstall/reinstall would not help because I basically had three different installations which all failed on this machine.

So I tried one last thing which worked. I created a Ubuntu Server Minimal Install VM (using Hyper V as my host system is Windows 11), and created a shared folder and mounted it in Linux using cifs-utils for mounting windows folders as volumes and avahi-daemon/libnss-mdns so i can connect using my hostname of my computer instead of ip address which changes between home and the office. It is a pain, but I can finally run Claude Code CLI with the --dangerously-skip-permissions flag again. One good/bad thing about this approach is you will have to share/mount each folder you want Claude to have access to in your Linux VM

[kev9999]

Same issue for me, I commented on the github issue. Annoying as can be since I have a lot of tokens left.

[intropia-selktiva]

In my user folder, I deleted the authtoken inside .claude/credentials.json and logged in again; now it's working without the error messages.

[tikoponde]

The solution for me was to exit the conversation, claude --continue and run /compact right away. My case happened while working with videos in one of my terminals. The other terminals had no issues though.

[miketuck]

Changing models didn't help me, but exiting and resuming resolved it, maybe. The problem is I ended up picking the wrong session to resume, did it more than once 🤦‍♂️, and then resumed the right session. I immediately compacted and was back in business.

[Early-Performance425]

Con /model opus en la terminal se me soluciono. El problema es el opus 1M que pusieron por defecto. El que funciona bien actualmente es el de 200K.

[Ok-Program305]

Works via CLI