When does the Claude Code limit reset?

The 5-hour window is rolling — usage from roughly five hours ago continuously falls off, so short breaks restore capacity gradually rather than at a fixed hour. The weekly cap resets on a fixed weekly schedule shown in the lockout message. /status (or the usage indicator) shows where you stand before you slam into either.

Explainer

Claude Code usage limits, explained — and what to do when you hit one

Q: What are the Claude Code usage limits in 2026?

Two meters run at once on every Claude subscription: a 5-hour rolling window and a weekly cap. Both scale with your plan (Pro, Max 5x, Max 20x). The 5-hour caps were doubled on May 6, 2026, and weekly caps got a +50% boost through July 13 — but the two-meter structure is unchanged: heavy days spend the window, heavy weeks spend the cap.

Q: Why did I hit the limit so fast?

Agent sessions are input machines: every turn re-reads files, diffs, and history, so one long unscoped session can burn what feels like a day of "chat" usage in an hour. Big pastes, huge context, and letting sessions run without /compact all accelerate it.

Q: How do I keep working after "usage limit reached"?

Four honest options: wait for the rolling window to free up; buy extra usage at API rates if your plan allows it; switch that task to a cheaper model or a second agent CLI; or hand the session context to a fallback agent. Backgrind automates the last one — its quota failover detects the lockout and offers to continue the work in a Grindy session in the same folder.

Priya Nair July 23, 2026 · 6 min read

Claude Code usage limits, explained — and what to do when you hit one

Every Claude Code power user eventually meets the same message mid-task: usage limit reached. It always feels random, and it never is. Claude subscriptions run two meters at once — a 5-hour rolling window and a weekly cap — and once you can picture both, the lockouts stop being surprises and start being schedulable. Here's how the system actually behaves in July 2026, and a playbook for the moment it says no.

The two meters

The 5-hour rolling window. Think of it as a bucket that drains continuously: what you used ~five hours ago falls off as new usage lands. Bursts are fine; sustained full-throttle agent work for hours is what empties it. These caps were doubled on May 6, 2026 — which tells you how many people were hitting them.
The weekly cap. The slower meter, sized per plan (Pro → Max 5x → Max 20x), on a fixed weekly reset. Anthropic ran weekly caps 50% higher through July 13, 2026 during the Fable 5 promo crunch; the structural point survives every adjustment: a heavy week can lock you out even when the 5-hour window looks fine.

The interplay is what catches people. A brutal Monday can leave your week thin by Thursday; a quiet week still won't save you from an unscoped afternoon that torches the rolling window. Neither meter cares that you were "almost done."

Why agent work burns limits faster than chat

A coding agent re-reads its world on every turn — files, diffs, tool output, its own history. Input tokens outnumber output by an order of magnitude, and your limit is spent on both. The practical levers, in descending order of impact: scope tasks tightly (an agent told exactly what to do reads less to figure it out), run /compact before long sessions drift, don't paste the world into the prompt, and route grind work to cheaper contexts — the fancy model doesn't need to write your test boilerplate. The same math drives paid-API costs, which we broke down in Fable 5's pay-per-token pricing — limits are just the subscription currency for the identical physics.

The lockout playbook

When the message lands mid-task, you have four moves:

Wait it out. If it's the rolling window, capacity returns gradually — a coffee and a code review often suffice. If it's the weekly cap, the reset time in the message is your answer, and waiting is probably not a plan.
Buy the overage. Max plans can purchase extra usage at API rates. Fine for a deadline; as a habit, run the math against current per-token prices first.
Have a second agent warm. This is the resilience argument from the Fable 5 suspension all over again, at smaller scale: if OpenCode or another CLI is already configured, "Claude is capped" downgrades from outage to inconvenience.
Hand off the context. The task doesn't care which model finishes it. The expensive part of switching is re-explaining state — which is exactly the part worth automating.

Frequently asked questions

What are the Claude Code usage limits in 2026?

Two concurrent meters on every plan: a 5-hour rolling window and a weekly cap, both scaled by tier. The 5-hour caps doubled May 6, 2026; weekly caps ran +50% through July 13. Heavy days spend the window, heavy weeks spend the cap.

When does the limit reset?

The rolling window frees up continuously as ~5-hour-old usage falls off. The weekly cap resets on the fixed schedule shown in the lockout message.

Why did I hit the limit so fast?

Agent sessions re-read context every turn — input dominates. Unscoped sessions, giant pastes, and skipping /compact burn the meters fastest.

How do I keep working after "usage limit reached"?

Wait for the window, buy overage at API rates, switch the task to a second CLI — or hand off the session context automatically, which is what Backgrind's quota failover does.

Where Backgrind fits

Backgrind treats the lockout as an event, not a dead end. Its quota failover watches the session for usage-limit exhaustion, and the moment Claude taps out it raises a decision card on every surface — overlay, phone, Fleet board. Accept, and the session's context hands off to a Grindy agent in the same folder; the work keeps moving while your window refills. Limits become a routing decision instead of a forced break — which is the whole point of not babysitting your agents.