Claude Code Reset Tracker
Tracks when Anthropic last flushed Claude Code usage limits
About Claude Code Reset Tracker
Claude Code Reset Tracker answers one question and does not pretend to answer any others: how long has it been since Anthropic last reset Claude Code usage limits? It watches announcements from the official developer account and from Claude Code team members, records each reset, and shows the elapsed time since the most recent one alongside the history.
It exists because usage limits are the part of a Claude Code subscription that most affects a working day, and the reset schedule is not published anywhere as a schedule. Resets are announced ad hoc, in posts that scroll away. If you are trying to work out whether a limit you have just hit is about to be cleared, or whether your plan is behaving normally this month, the only honest source is the announcement history, and this is that history in one page rather than a search through a timeline.
The site tracks resets announced publicly by Anthropic and Claude Code team members, timestamps them in UTC, and computes the interval since the most recent one. Curated data renders immediately and the live freshness check runs in your browser.
Alongside the counter it keeps a scorecard from the tracked period: how many resets have been recorded, the mean gap between them, the longest interval, and the announced rate per month. At the time of writing it lists twelve resets tracked, a 12.8 day average gap, a 47.6 day longest drought and a pace of 2.6 a month.
It also separates two things people conflate. The announced resets are Anthropic flushing counters across accounts; your own five-hour and weekly windows are personal and come from the /usage command inside Claude Code. The site provides countdown fields for your own limits but is explicit that they are not the same thing as an announced reset.
- •Time since the last announced reset - the single number the site exists for, in UTC, with a note where a reset applied only to some plans.
- •Reset history and scorecard - count tracked, average gap, longest drought and announcements per month, which together tell you whether the current wait is unusual.
- •RSS alerts - subscribe rather than check, which suits the actual usage pattern of wondering once and then forgetting.
- •A JSON endpoint - summary.json exposes the same data for anyone who wants to put it in a status bar or a script.
- •Personal limit countdowns - fields for your own five-hour and weekly windows, kept deliberately separate from the announced resets.
- •Free with no account - there is no paid tier, no signup and no pricing page.
Anyone running Claude Code enough to hit a limit. That is a narrow audience and the tool is scoped to match: it is a single page that loads fast, states one fact clearly, and offers a feed so you do not have to return.
It is most useful in the moment of hitting a wall mid-task, when the question is whether to wait or to switch to something else. Knowing that the average gap is around thirteen days, and that the longest recorded was closer to seven weeks, is more useful for that decision than refreshing a social feed. Treat the data as what it is: a record of public announcements, not an Anthropic-published schedule, and not a prediction of the next one.
