When does my Claude Code usage limit reset?
Claude Code has a rolling 5-hour limit and a weekly one on Pro and Max. Where to see exactly when each resets, and how to keep that time on screen as you work.
If you work in Claude Code on a claude.ai Pro or Max plan, two limits run in the background: a rolling five-hour window and a weekly one. Both are easy to forget until one is nearly used up, and at that point the question that matters is not the percentage. It is when it comes back.
Two windows, measured separately
Claude Code describes them as five_hour and seven_day. Each has a percentage used, from 0 to 100, and a resets_at time. They move independently: a heavy afternoon can fill the five-hour window while the weekly one is still low, and a steady week can do the opposite. Watching one tells you nothing about the other.
Where the reset time comes from
The same numbers Claude Code uses are handed to your status line script with every update. resets_at is Unix epoch seconds, which makes it easy to turn into something readable. On macOS, date -r 1790544264 '+%a %-d %b %-I:%M%p' prints the day, date and time; on Linux, date -d @1790544264 does the same.
Two details make the difference between a reset time you can trust and one you cannot:
- Say the date when it is not today. A five-hour window that resets at 12:10AM is tomorrow, and a weekly one can be days away. A bare clock time reads as today and is wrong.
- Keep it current. Claude Code re-runs the status line when a window reaches its reset time, but a countdown otherwise only moves on events. Set
refreshIntervalin the status line settings so an idle session does not show a stale one.
Countdown or clock time?
A countdown answers whether to keep going now: in 40 minutes, probably wait. A clock time answers when to come back: Monday at 5:50AM. We show both when there is room and the clock time alone when there is not, because the clock time is the one you cannot work out in your head.
| Window | Countdown | Exact |
|---|---|---|
| 5-hour | in 4h 19m | Sat 26 Sep 12:10AM |
| Weekly | in 2d 10h | Mon 28 Sep 5:50AM |
Why the limit might not show at all
The limit data appears only for claude.ai Pro and Max subscribers, and only after the first reply in a session. Each window can be missing on its own, and Claude Code drops one once its reset time passes. A status line should treat all of that as normal and simply leave the capsule out, rather than printing zero, which reads as a limit fully available.
Context is a separate budget with its own warning signs; what a skill costs you in context covers that side. For both on one line, with each reset written as an exact time and date, see Capsule Status Line.
Questions
How many usage limits does Claude Code have?
On a claude.ai Pro or Max plan, Claude Code reports two windows: a rolling five-hour one and a seven-day one. Each has its own percentage used and its own reset time.
Can I see the exact reset time rather than a countdown?
Yes. Claude Code gives a status line script each window's reset time as Unix epoch seconds, so the script can print it as a clock time, with the day and date when it is not today.
Why is there no usage limit in my status line?
The limit data is only sent for claude.ai Pro and Max subscribers, and only after the first reply in a session. On an API key there is nothing to show, which is expected rather than broken.