[BUG] Claude usage limit reached. Your limit will reset at 3pm
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 experiencing an unusual and persistent issue where the token usage limit for Claude Code is not resetting as expected, leading to a lockout that has lasted over 24 hours.
Normally, the usage tokens seem to reset every 5 hours. However, since 4:00 PM yesterday (Wednesday, October 8th), I have been unable to use the service.
The application currently indicates that the tokens will reset at 3:00 PM today (Thursday, October 9th), which is a full 23-hour gap since I was locked out, and significantly different from the usual 5-hour cycle.
What Should Happen?
The token usage should reset approximately every 5 hours, or at minimum, the 24-hour reset limit should be correctly calculated and implemented to prevent a full-day service interruption.
Error Messages/Logs
Claude usage limit reached. Your limit will reset
at 3pm (America/Santiago).
Steps to Reproduce
1.-Open the terminal or the client interface where you typically interact with Claude Code (e.g., Cursor IDE's AI chat/prompt window).
2.-Attempt to send any prompt or command to Claude Code.
3.-The service immediately returns the following message, indicating the limit has been reached and the reset time is delayed/incorrect:
-Claude usage limit reached. Your limit will reset at 3pm (America/Santiago).
Context: The issue is not dependent on the content of the prompt; any attempt to utilize the service while locked out triggers this exact response. This message has persisted for almost 24 hours, despite the normal 5-hour reset cycle.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.0.39
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Cursor
Additional Information
_No response_
This issue has 12 comments on GitHub. Read the full discussion on GitHub ↗