Usage limit resets in AI coding tools: rolling, weekly and monthly clocks
Claude Code, Codex, Cursor and Copilot reset on different clocks. Here is which is which and where to see the next reset.
By ClaudeGPT Si Newsroom, Editorial team
3 min read
Usage limit resets in AI coding tools run on three kinds of clock: a rolling window of a few hours, a weekly window, and a monthly or billing-cycle reset. Knowing which clock your tool uses tells you whether to take a coffee break or switch tools for the day, and UsageAtlas, a free and open-source desktop app, shows the next reported reset for several tools on one screen.
Rolling, weekly and monthly clocks
Rolling windows start counting from your activity and clear a few hours later. Claude Code on Pro and Max has a five-hour session limit. Codex estimates usage per five-hour period on Plus and Standard Business plans; its docs say Pro plans currently have no five-hour limit.
Weekly windows sit on top of the short ones. Claude Code has a weekly limit alongside the session limit, and the two count at the same time, so a big burst can drain the week before the session clock resets. Codex says weekly limits may also apply. Cursor's newer subscription refreshes its included pool weekly, separate from the billing date.
Monthly resets follow the calendar or the billing cycle. GitHub Copilot's AI credit allowance resets at 00:00:00 UTC on the first day of each calendar month, and unused credits do not carry over. Cursor's legacy individual plans reset included usage monthly with the billing cycle.
Reset clocks at a glance
| Tool | Short window | Long window | How to see the next reset |
|---|---|---|---|
| Claude Code | Five-hour session | Weekly | Limit messages print it; /usage |
| Codex | Five-hour on some plans | Weekly, may apply | /status in the CLI |
| Cursor | None stated | Weekly pool or monthly, by plan type | Cursor dashboard |
| GitHub Copilot | None stated | Calendar month, UTC | GitHub billing settings or IDE icon |
Sizes change often, so this table leaves out numbers on purpose. The shape of the clock changes far less.
Find the next reset without guessing
Each tool exposes its own reset somewhere. Claude Code prints it in the limit message, for example "resets 3:45pm", and shows plan usage in /usage. Codex shows rate limits in /status. Copilot and Cursor keep theirs in the web dashboard, and Copilot also shows usage from the status icon in supported IDEs.
The friction starts when your week uses more than one of these. A rolling Claude Code window, a weekly Codex limit and a monthly Copilot allowance all move at different speeds, and nothing in any one of them tells you about the others.
One reset view with UsageAtlas
UsageAtlas is a desktop tracker that reads supported limits from Claude Code, Codex, Cursor, GitHub Copilot, Warp, Kimi Code, Kilo Code, Factory / Droid, Amp and Qoder, and lists remaining capacity next to the reported reset time for each window. Set a remaining-capacity threshold per window and it sends one alert per reset cycle, so you hear about it once rather than on every request.
It is free and open source under the MIT license, runs on Windows, macOS and Linux, and works without an account. An optional free account saves your history. Prompts and responses are never read.
Reported resets can lag behind the provider, and cost figures in the app are estimates. If you only use one tool, its own command already tells you the reset; UsageAtlas earns its place once you juggle several clocks.
FAQ
Do all AI coding limits reset at midnight? No. Some roll from your own activity, some reset weekly, and Copilot resets on the first of the month in UTC.
Does switching models reset my limit? In Claude Code, session and weekly limits are shared across models, so switching does not help; per-family Opus or Sonnet limits are the exception.
Can UsageAtlas show resets for every tool? Only where the provider reports one. Local-history sources like OpenCode have no reset clock in the app.