[BUG] UI spams /rate-limit-options commands after rate limit expires
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?
After hitting the rate limit and waiting for it to reset, attempting to type any message causes the Claude Code UI to automatically spam
/rate-limit-options or /reset-rate-limit commands repeatedly. These appear to be internal commands that aren't exposed through the normal /
autocomplete feature. The UI becomes unusable until running /compact or restarting.
What Should Happen?
After the rate limit timer expires, I should be able to type normal messages and continue the conversation without the UI spamming internal rate
limit commands.
Error Messages/Logs
No specific error messages displayed. The UI simply starts auto-sending:
/rate-limit-options
or
/reset-rate-limit
These commands appear repeatedly after user input.
Steps to Reproduce
- Use Claude Code normally until hitting the rate limit
- Wait for the rate limit timer to expire (wait for the time when you can work again)
- Try to type any message (e.g., "hello")
- Observe the UI automatically spamming
/rate-limit-optionsor/reset-rate-limitcommands - Note: These commands don't appear in normal
/autocomplete and aren't user-facing commands
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.72 (Claude Code)
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
xfce4-terminal
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.2
ID=debian
- This issue has occurred at least twice now under the same circumstances
- The commands being spammed (/rate-limit-options, /reset-rate-limit) don't appear to be legitimate user-facing slash commands
- Running
/compactappears to break the loop and restore normal functionality - The issue specifically triggers after waiting out a rate limit and then trying to interact again
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗