When does the Claude Code limit reset? Four places to find the time
The five-hour window rolls and the weekly one resets once a week. Here is where your own reset times show up.
By ClaudeGPT Si Newsroom, Editorial team··3 min read
A Claude Code limit reset happens on two schedules: the session limit resets on a rolling five-hour window, and the weekly limit resets once a week at a set day and time. The exact time for your account is printed in the limit message, in /usage, on claude.ai and in UsageAtlas, a free, open-source desktop app that shows both resets in your local time.
The short answer
Anthropic's help center describes a session limit that resets every five hours and a weekly limit that resets once a week. Both apply to Pro and Max, and to Team and Enterprise seats. Because the five-hour window rolls, the reset time is not the same every day; it depends on when you started using it. Anthropic does not publish one global reset clock, so read yours from one of the places below.
Four places to find your reset time
The limit message itself
When a window runs out, Claude Code prints the reset in the message:
- "You've hit your session limit · resets 3:45pm"
- "You've hit your weekly limit · resets Mon 12:00am"
The same reset appears in the warning you get before the limit, for example "You've used 85% of your session limit · resets 3:45pm".
The /usage command
Run /usage inside Claude Code for plan usage bars and when each limit resets. On paid plans it also lists what used your limits, such as subagents and MCP servers. If you see "rate limited until" a time on that screen, it refers to fetching the usage data, not to your coding.
Settings > Usage on claude.ai
The account page shows real-time consumption. It is also where Pro and Max users turn on usage credits, which keep Claude Code working past a limit at standard API rates.
A desktop tracker: UsageAtlas
UsageAtlas shows the supported Claude five-hour and weekly windows, the capacity left in each and the local reset time, without a session open. Set a threshold per window and it sends one desktop alert per reset cycle. It is free and open source, runs on Windows, macOS and Linux, and needs no account for local tracking. Cost figures in it are estimates, and provider data can lag, so check /usage too if a deadline depends on the exact minute.
Side by side
| Place | Shows five-hour reset | Shows weekly reset | Works outside a session | Alerts |
|---|---|---|---|---|
| Limit message | Yes | Yes | No | No |
/usage |
Yes | Yes | No | Warning near the limit |
| claude.ai Settings > Usage | Usage view | Usage view | Yes | No |
| UsageAtlas | Yes | Yes | Yes | One per cycle |
Developers who want the figure in the terminal can also add the status line fields rate_limits.five_hour.resets_at and rate_limits.seven_day.resets_at, which give the reset as a Unix timestamp on Pro and Max.
What happens at the reset
In an interactive session signed in with a subscription, Claude Code (v2.1.234 and later) can wait and continue the interrupted task once the limit resets. Leave the session open; it shows "Continuing automatically" with the time, and Esc cancels. If you exit, the wait does not restart when you resume.
FAQ
Does the Claude Code weekly limit reset at the same time for everyone?
Anthropic does not publish one shared time. Your limit message and /usage show the day and time for your account.
Does switching models reset the limit? No. The session and weekly limits cover all models. Only the separate Opus and Sonnet limits can be avoided by switching model family.
Can I reset the limit early? Not as such. Usage credits or a plan upgrade let you keep working before the reset.