[BUG] Claude usage limit reached. Your limit will reset at 3pm

Status Closed — not planned
Maintainer reply None cached
Activity 12 comments · opened Oct 9, 2025 · closed Apr 1, 2026

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_

View original on GitHub ↗

12 Comments

github-actions[bot] · 10 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/9048
  2. https://github.com/anthropics/claude-code/issues/9005
  3. https://github.com/anthropics/claude-code/issues/8958

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

jkudish · 10 months ago

Same here, looking at my usage settings page https://claude.ai/settings/usage I see that opus is maxed out, but i'm trying to use sonnet as confirmed by /model

I think they're accidentally routing sonnet calls to opus maybe?

<img width="1069" height="716" alt="Image" src="https://github.com/user-attachments/assets/34ffd72e-c39a-4599-ac86-52828acd87cd" />

<img width="2202" height="392" alt="Image" src="https://github.com/user-attachments/assets/e484afce-2f07-4429-bdbf-1de063fc1ae5" />

info656 · 10 months ago

I have a similar experience. My usage of Opus is at 95%, and now even accidentally querying Opus once a day immediately blocks access to everything—that's what I just did now. I understand that Claude is trying to limit usage somehow, but this seems to me like a punishment for using the services, when it blocks access to everything as a penalty. We're not children.

Nothing else remains but to find a replacement for Claude. They are certainly not irreplaceable, and I think that this usage policy of Claude, which is unclear and punitive, will ensure a loss of customers for them. And in the end, I wish that for them too.

videni · 9 months ago

Now it resets every five hours, which is so frustrating. I think they just changed the policy.

github-actions[bot] · 8 months ago

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.

SamuelChojnacki · 7 months ago

same here ⎿  You've hit your limit · resets 3pm (Asia/Tbilisi)

10a5er · 7 months ago

⎿  You've hit your limit · resets 6pm (UTC)

❯ /usage

Current session
██████████████████████████████████████████ 84% used
Resets 5:59pm (UTC)

Current week (all models)
██████████████████████████████ 60% used
Resets 4:59pm (UTC)

JakubLog · 6 months ago

Same issue here!

● Agent "Read key frontend files" completed
⎿ You've hit your limit · resets 1am (Europe/Warsaw)

<img width="1047" height="414" alt="Image" src="https://github.com/user-attachments/assets/a8569713-737b-498a-87d4-6a0deff10584" />

alarmdev · 6 months ago

why is Claude having this limit on a paid version??? I am sure some other tool will take over this space soon and you have will no valued customers. You’ve hit your limit for Claude messages. Limits will reset at 4:00 AM.

10a5er · 6 months ago
why is Claude having this limit on a paid version??? I am sure some other tool will take over this space soon and you have will no valued customers. You’ve hit your limit for Claude messages. Limits will reset at 4:00 AM.

bc what you get out of the payed plan is far far more than what you would get with a pay-as-you-go API, thats why everyone is so pissed you cant use the payed plan like a API anymore in other tools. — The issue is not the limit, its that its either displayed wrong or applied to early inside claude-code.

There are other solutions without a limit, but either they have a very small context-window, use your data for profit, or get capital from sectors which are well below the ethical standarts anthropics try to keep.

github-actions[bot] · 5 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 4 months 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.