[BUG] /rate-limit-options command repeatedly auto-executes after session reset, causing excessive token consumption

Resolved 💬 28 comments Opened Dec 16, 2025 by kalinzt Closed May 18, 2026
💡 Likely answer: A maintainer (claude[bot], contributor) 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?

Issue Description:

After a session reset (context limit reached), the /rate-limit-options command is automatically and repeatedly
executed without user intervention, causing significant issues:

Problems:

  1. Terminal interference: The repeated command execution causes constant terminal refreshes, disrupting workflow
  2. Forced compact operation: User is forced to run /compact to clear the repetitive messages
  3. Excessive token consumption: The forced compact operation consumes 20%+ of available tokens
  4. Workflow disruption: The combination of auto-refreshing terminal and forced compact makes it difficult to continue work

What Should Happen?

Expected Behavior:

  • Session should reset cleanly without auto-executing commands
  • /rate-limit-options should only execute when user explicitly requests it
  • Session continuation should not require forced compact

Actual Behavior:

  • /rate-limit-options auto-executes repeatedly after session reset
  • Terminal becomes unusable due to constant refreshing
  • User must waste 20%+ tokens on compact to continue working

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Work on a project until session context limit is reached
  2. Session automatically resets/compacts
  3. Observe /rate-limit-options command being executed repeatedly
  4. Terminal continuously refreshes with rate limit option outputs
  5. User must run /compact to regain control
  6. Compact operation consumes significant tokens

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.67 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

Impact:

  • High: Severely disrupts workflow and wastes tokens on non-productive operations
  • Makes long coding sessions impractical due to token waste

Environment:

  • Claude Code CLI
  • Session continuation after context limit/reset

View original on GitHub ↗

28 Comments

aterveus · 7 months ago

I'm having the same issue while using Claude Code CLI outside of VS Code too.

benzntech · 7 months ago

When auto-compact happens due to context limits, /rate-limit-options is included in the compacted conversation history and becomes part of the project context. This causes the conversation to stop and get disrupted. The /rate-limit-options should be excluded from auto-compact operations so it doesn't interfere with the actual conversation context when resuming. It should be treated as a system/diagnostic command, not part of the conversation history.

radimt8 · 7 months ago

Having a similar issue - the same command pops basically almost every time I toggle between verbose output and normal mode. Upon return to normal I can see that "I have already sent" this exact command

istvan-ujjmeszaros · 7 months ago

Extremely annoying bug, please fix ASAP.

aniltan · 7 months ago

Having the same issue here.

hqvisionsadmin · 7 months ago

same, didnt see this issue. one thing to note for me is I got it while I was RDPd into computer

https://github.com/anthropics/claude-code/issues/14505

myrtillecomte-arch · 6 months ago

Same problem. As soon as I hit the rate limit in a discussion, everytime I switch between thoughts explicit or not (ctrl-o by default) the /rate-limit-options is spammed. Claude loses precious tokens trying to understand what I mean, and its context & train of thought gets polluted. This is extremely frustrating !

taylorasdfjkl · 6 months ago

I just experienced this issue using Claude Code v2.0.72.
I hit my rate limit and then enabled extra usage.
After adding $5 to my account, it started spamming the model with "/rate-limit-options" repeatedly and then pretty much burned through my extra usage.
Reloading the app fixed it.

kings-nexus · 6 months ago

Press Ctrl + C to interrupt the current task, then use claude -r to resume the task; this can temporarily circumvent this problem.

rstoddard24 · 6 months ago

same issue - claude version 2.0.73 running cli on Mac

george-assan · 6 months ago

Have the same issue.. claude cli version v2.0.72 running on Mac

anantham · 6 months ago

Please fix this asap, I see this in my macbook cc version : 2.0.76

jeidsath · 6 months ago

Seeing this intermittently on mac claude cli 2.0.76

ThroughIris · 6 months ago

yes same here, every time Claude code produces this slash command. It erases everything that I have in the input box which is frustrating. It is interesting that it seems to also surprise or confused Claude I can see in the thinking traces that they see the / command that is produced and are confused by it, so I can only guess it's getting automatically injected frequently, and while I'm far away from hitting my right limit

EasyaspieDeFi · 6 months ago

This just happened to me as well. After my previous session ran out of tokens and I restarted the task in the current session Claude started spamming /rate-limit-options and within a minute or two blasted through nearly a quarter of my current session usage on sonnet 4.5.

rpsirois · 6 months ago

I'm using Claude Code for the first time and ran into this right away. It spams the terminal so much that you have to race it with Ctrl+C to exit claude. I did legitimately hit my "usage" limit though. I asked it to exhaust the last few percent of the usage doing some research on a coding plan and document as it went which apparently was a mistake? Not very familiar with this, but it certainly feels like a bug.

IlyaGulya · 6 months ago

Still happens in Claude Code 2.1.5

<img width="1123" height="452" alt="Image" src="https://github.com/user-attachments/assets/46037384-f1b5-48dd-ad02-926a71cf9444" />

Angelopaolo23 · 6 months ago

I have the same error too, with the command /rate-limit-options that sends as a prompt automatically.
I'm using the 2.1.5 version of claude code.

<img width="810" height="1039" alt="Image" src="https://github.com/user-attachments/assets/73f1c5e3-257c-4d0e-9779-9c8276c456c7" />

umjammer · 6 months ago

unbelievable

<img width="463" height="1546" alt="Image" src="https://github.com/user-attachments/assets/2ba68e9b-c90b-429b-8c50-c16d9f2a9e88" />

Claude Code v2.1.7

seinfold · 6 months ago

<img width="311" height="636" alt="Image" src="https://github.com/user-attachments/assets/af201e2c-8ecc-472f-9bac-4778aacc94c8" />

RafalekS · 5 months ago

same issue on WIN11 Claude Code v2.1.12

mgdelmonte · 5 months ago

same on Win11 Claude Code v2.1.14

nik-suri · 5 months ago

Same on mac OS, using claude v2.1.29

Specifically, I encountered this issue when I ran out of usage on the Pro plan, and then enabled and bought a small amount of extra usage credits, and then attempted to continue from where I had last left off with claude code.

yethranayeh · 5 months ago

Same on macOS Sequoia Version 15.6.1, Claude Code v2.1.31 and Claude VSCode extension v2.1.31
After getting to 71% session usage, I saw /rate-limit-options being called and then the CLI just started showing incorrect session usage at 100% and also 90% (the yellow warning at the bottom right), just bugging out in general. Running /usage would still show the correct usage as 71%.

So, I tried /clear and also just starting a new instance, but it was still happening:

<img width="452" height="392" alt="Image" src="https://github.com/user-attachments/assets/dd22b7fa-d242-4d7f-ac2c-aa70e22f539e" />

---

After not being able to continue on CLI, I downloaded the VSCode extension to continue working on my code. It started streaming some response text, but it also then claimed that the session limit was reached even the /usage result begs to differ:

<img width="679" height="300" alt="Image" src="https://github.com/user-attachments/assets/6a2c8b19-5268-4a33-b329-b1c268525bfd" />

---

Finally, I downloaded Claude Desktop as last resort, and was able to chat with it like expected. I then moved past the 71% usage and filled it up to 98%

<img width="931" height="411" alt="Image" src="https://github.com/user-attachments/assets/ae8abf44-7d99-4a19-ad7e-b6c45c5af787" />

The window on the left is Claude Desktop, after I spent the remaining session credits there. The window on the right is Claude Code, claiming yet again that I hit my limit, even though I am at 98%.

I have been using Claude Code at work for weeks, and had no problems with it. So, I wanted to get it for myself to develop some personal stuff and this is what I am facing on my first ever session.

At work, I use both a Windows 11 machine and a Ubuntu Server, both of which worked without issue so far.

cerinawithasea1 · 5 months ago

<img width="967" height="552" alt="Image" src="https://github.com/user-attachments/assets/98b9a8f4-ab0f-40a1-88c5-42a5eb20feed" />
i have a few accounts and this continued on one for 5 days (fin stopped speaking to me) no use so i closed the account opened a new one. it worked for a day and groundhogs day
now i have paid for 2 accounts i can not use (i am at 5 accounts now i could have a business account)
I am on am M1 2020 MacBook Air OS 15.5 sshed into an ubuntu server Claude Code 2.1.31

monjeyer · 4 months ago

Also having this bug. Super annoying!

claude[bot] contributor · 1 month ago

This is a duplicate of #41719, which was fixed as of version 2.1.90.

github-actions[bot] · 8 days 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.