Claude Code rate limit reset calculator
Claude's usage limit runs on a rolling 5-hour window that starts with the first message you send after a fresh window. Tell it when that first message went out and it shows exactly when the window resets, with a live countdown. All in your browser, nothing stored.
The 5-hour clock starts on that first message, not on your last one. Times use your device's local clock.
How the Claude Code usage limit actually works
- The 5-hour window is rolling. It opens on your first message and closes 5 hours later. Everything you send in between counts against that one window. When it closes, your allowance refreshes and the next message you send opens a fresh 5-hour window.
- There's also a weekly cap. On top of the 5-hour windows, plans have a rolling 7-day limit. You can hit the weekly wall even with a fresh 5-hour window, which is the part that surprises people mid-project.
- Different models can draw on different pools. Anthropic has shifted how models share limits over time, so treat any single number as a moving target and watch your own meter.
The practical trick: start your biggest, longest agent runs right after a window resets, so you have the full 5 hours before a limit can interrupt a long build. The calculator above is for planning that. The catch is you have to be watching to know where you are.
The problem a calculator can't fix
Knowing your reset time helps you plan. It doesn't help when a run stalls the moment you step away, or when you hit the wall 40 minutes into something and only find out by going back to the terminal. That's the gap DevFob was built for (disclosure: it's our product): a live usage meter for every Claude login in your Mac menu bar and on your phone, so you see the 5-hour and weekly windows at a glance, plus the agent's actual questions pushed to your phone or watch so a stalled run gets unblocked instead of sitting there. Local, no account, end to end encrypted.
This tool models the documented rolling-window behavior; Anthropic's exact limits vary by plan and change over time, so treat the result as a planning estimate, not a guarantee. Accurate as of July 2026. Spot an error?