Claude resets
Read-only MCP for announced Claude Code usage-limit resets, with Codex comparison. Not affiliated with Anthropic.
Hosted MCP Server
npx add-mcp 'https://claude-resets.com/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Resets tracked
16
Announcements that flushed the counters, plus 3 banked resets.
Average gap
13.9 days
Mean time between consecutive resets.
Longest drought
48.1 days
The most patience ever required.
Pace
2.3 / month
Announced resets per month across the tracked period.
The Claude archive Every tracked announcement, newest first.
Every tracked announcement, newest first.
- Banked reset Pro, Max, Ultra + Team One free full reset for all Pro, Max, Ultra and Team users, across all models and limits, usable until December 10 at 2:00 PM PT. Anthropic offered it to make up for recent issues that used more limits than intended, including Fable resets that did little for users who had already hit their weekly limits across all models. 1.1 days after the previous reset Original post ↗
- Banked reset paid plans Eligible paid accounts get a Fable 5.2 reset grant: Max/Ultra and premium Team/legacy seat-based Enterprise receive 1–3 by paid tenure (under 6 months: 1; 6–12 months: 2; over 12 months: 3); Pro and standard Team receive one. Each restores only Fable usage on the weekly meter; other weekly usage stays spent. It also refills the 5-hour window if the account has one. 48.1 days after the previous reset Original post by @bcherny ↗
- Banked reset Pro, Max + Team Launched Opus 5.5 with 20% higher 5-hour session limits, and gave Pro, Max and Team users a banked reset to apply any time until October 22. 17.9 days after the previous reset Original post ↗
- ResetMax* Reset weekly limits for everyone on a Claude Max plan after Fable 5.1 launched, so people could keep building over the long weekend. 3.1 days after the previous reset Original post by @lydiahallie ↗
- Resetall Shipped Fable 5.1 and reset 5-hour and weekly limits for all users. 47.6 days after the previous reset Original post ↗
My limit countdowns 5-hour and weekly windows from /usage — saved on this device.
Enter the next reset times shown by Claude Code’s /usage screen. These are your personal rolling windows, separate from the announced resets tracked above.
Saved only in this browser
Time remaining Not set
Time remaining Not set
When a countdown reaches zero, check /usage again—the rolling window may move after new activity.
Claude vs Codex Head-to-head resets, pace, and droughts.
Window
Table view — every number on this page
Claude Code reset questions Predictions, plan labels, limit changes and alerts.
Does a Claude reset apply to every plan?
It depends on the announcement. Some resets cover everyone; others cover particular plans, or only the users hit by a specific issue. Each entry in the Claude reset archive shows the plans it covered.
Is a limit increase the same as a reset?
No. A reset restores usage by clearing the usage counters for the plans it covers. A limit increase raises the allowance without necessarily clearing them. The archive lists both, but only resets count toward the statistics here. Banked resets, which you apply yourself later, count as resets too.
How can I get Claude Code reset alerts?
Subscribe to the reset-only RSS feed, or turn on browser alerts with Enable reset alerts at the top of the page, where your browser supports them. Alerts go out as soon as a reset is detected. A detected reset is marked “Awaiting review” and joins the archive unless it is withdrawn.
To follow resets in a calendar, subscribe to the reset calendar in Apple Calendar or Outlook, or add it to Google Calendar. Each reset becomes an event, and so does the last day to apply a banked reset.