### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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? Sometime around 2 pm I got my limit reached and it said it will reset at 5:20 pm, so I logged in around 8:30 and was working when limit reached again and

[BUG] Incorrect usage reset time for daily limit, for a 5:20-10:20 window, at 9 it is indicating 4 hours left to reset, weekly limit is on 50%

Status Fixed / completed

Maintainer reply None cached

Activity 3 comments · opened May 6, 2026 · closed May 7, 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?

Sometime around 2 pm I got my limit reached and it said it will reset at 5:20 pm, so I logged in around 8:30 and was working when limit reached again and it was around 9 so it should reset in like 1 hour and 20 minutes but something strange happened, it said 4 hours left before reset of limit, which means around 1 am!

5:20-10:20 pm then 10:20-3:20 ideally be the 5 hour limit.

And weekly limit is a 50%

What Should Happen?

5:20-10:20 pm then 10:20-3:20 ideally be the 5 hour limit. Not extended till 1 am (beyond 5 hour, 9 hours to be exact)

Error Messages/Logs

Steps to Reproduce

It came automatically and claud fin agent told me to report it here

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Latest

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

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

yurukusa · 5 months ago

This is a clean Trigger 4 evidence shape. The 4-to-9-hour gap between the displayed reset and the actual 5-hour window matches the failure mode that has been accumulating in the weekly-quota-reset cluster since at least #47855832 from late April.
One thing worth checking on your end: is the displayed countdown reading from /usage --json or from the TUI status line? They have diverged in past version pairs, with the TUI continuing to show a stale value while /usage --json returned the corrected one. If you can compare the two side by side at the moment the countdown looks wrong, that distinguishes a UI staleness bug from a server-side timer bug, which matters for whichever maintainer picks this up.
The 2026-05-06 16:17 UTC announcement doubled the 5-hour rate limits but did not change the weekly-window timer mechanism. Reports filed after that announcement are useful precisely because they isolate the timer dimension from the rate-limit-size dimension. Worth keeping the report open and visible.

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