You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Usage Limit Reset Inconsistency with Documented 5-Hour Interval #8084
Bug Description
I'm using claude code on the team plan with the premium subscription. I see the documentation says there are limits that reset every five hours. However, I'm getting a message that says I am approaching my limit and it will reset at 10 am tomorrow, which is about 16 hours from now. I can't find any documentation that would explain this and it seems like a bug.
This is the documentation I'm finding: https://support.claude.com/en/articles/11845131-using-claude-code-with-your-team-or-enterprise-plan
And this is the message I'm getting in Claude Code: Approaching usage limit · resets at 10am
Hi team — just adding my case here since my original issue was auto-flagged as a duplicate.
On a Claude Max 20x account, I am seeing a much more extreme version of this bug:
VS Code Claude Code terminal shows:
“Claude usage limit reached. Your limit will reset at Oct 7, 1am.”
→ That’s a 6-day lockout, not just a few hours.
The same lockout appears on my Claude AI web app (same account).
Environment:
Windows 10, VS Code (latest Claude Code extension), Chrome (latest).
Started on Sep 30, 2025, ~3PM SGT.
Expected: Reset every 5 hours (Max 20x) — not multiple days.
Actual: Account stuck in a 6-day reset window.
Attachments:
I’m adding screenshots of the errors seen on both Claude Code (VS Code terminal) and Claude AI web app for reference.
I’ve already opened a support ticket (escalated Oct 1), but wanted to document this here for visibility, since it may be a more severe manifestation of the same reset bug.
After my initial bug report, I later hit a limit that also said it would reset on Oct 30th at 10AM, which at the time was 6 days in the future. I was wondering if I was hitting some sort of weekly limit. I also wondered if perhaps I accidentally triggered some sort of fraud/account-sharing detection since I got the 6-day reset after going to my sister's house and would have had a new IP. Totally guessing here
After my initial bug report, I later hit a limit that also said it would reset on Oct 30th at 10AM, which at the time was 6 days in the future. I was wondering if I was hitting some sort of weekly limit. I also wondered if perhaps I accidentally triggered some sort of fraud/account-sharing detection since I got the 6-day reset after going to my sister's house and would have had a new IP. Totally guessing here
Support didn’t reply me and I just found out about this article. It seems not to be technical glitch but anthropic is applying new weekly reset limit for power users
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
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.
Activity
elfieelfieelfie commentedon Oct 1, 2025
Hi team — just adding my case here since my original issue was auto-flagged as a duplicate.
On a Claude Max 20x account, I am seeing a much more extreme version of this bug:
VS Code Claude Code terminal shows:
“Claude usage limit reached. Your limit will reset at Oct 7, 1am.”
→ That’s a 6-day lockout, not just a few hours.
The same lockout appears on my Claude AI web app (same account).
Environment:
Windows 10, VS Code (latest Claude Code extension), Chrome (latest).
Started on Sep 30, 2025, ~3PM SGT.
Expected: Reset every 5 hours (Max 20x) — not multiple days.
Actual: Account stuck in a 6-day reset window.
Attachments:
I’m adding screenshots of the errors seen on both Claude Code (VS Code terminal) and Claude AI web app for reference.
I’ve already opened a support ticket (escalated Oct 1), but wanted to document this here for visibility, since it may be a more severe manifestation of the same reset bug.
elfieelfieelfie commentedon Oct 1, 2025
Hi team — I’d like to add more context from my case:
The usage limit lockout in my Claude Max 20x account only affects Claude Opus 4.1.
Claude Sonnet 4.5 still works normally without any reset or lockout on my account.
This indicates the bug is likely in the Opus quota / reset logic, not a general account-level counter.
My Opus terminal message: “Claude usage limit reached. Your limit will reset at Oct 7, 1am.”
I’ve already uploaded screenshots from both Opus and Sonnet views, plus included my support ticket escalation.
Please consider this variant when developing the fix. See screenshots.
dtarico-suplari commentedon Oct 2, 2025
After my initial bug report, I later hit a limit that also said it would reset on Oct 30th at 10AM, which at the time was 6 days in the future. I was wondering if I was hitting some sort of weekly limit. I also wondered if perhaps I accidentally triggered some sort of fraud/account-sharing detection since I got the 6-day reset after going to my sister's house and would have had a new IP. Totally guessing here
elfieelfieelfie commentedon Oct 2, 2025
Support didn’t reply me and I just found out about this article. It seems not to be technical glitch but anthropic is applying new weekly reset limit for power users
https://techcrunch.com/2025/07/28/anthropic-unveils-new-rate-limits-to-curb-claude-code-power-users/
waramity commentedon Oct 5, 2025
same, Claude Opus 4.1 show limit usage reached for 3 days.
dtarico-suplari commentedon Oct 22, 2025
Claude 2.x has an improved /status command. You can tab over to the usage to see your percent usage for session limits as well as weekly and Opus
github-actions commentedon Dec 8, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
github-actions commentedon Jan 8, 2026
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
github-actions commentedon Jan 16, 2026
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.