Table of Contents
You finally hit your stride in Claude Code, and then this stops you cold:
Claude usage limit reached.
Your limit will reset at 3pm (America/New_York)."You have used up what your current plan allows, for now." It is not an error or a bug: it is how the Pro / Max subscription usage limits work. The frustrating part is that it is not obvious why it ran out so fast, when it comes back, or what you can do until then. This article lays out the two-tier limit structure (5-hour + weekly), what drives consumption, what to do the moment you hit the cap, how to check what is left, and the API escape hatch — based on official information.
Three takeaways up front. (1) The limit is two layers: a "rolling 5-hour window" and a "weekly window" (Max also has a separate weekly cap just for Opus). (2) The biggest consumer is your model choice — Opus burns through the allowance far faster than Sonnet. (3) When you cannot wait, the clean moves are "drop to Sonnet / trim context / switch to pay-as-you-go API." Note that the displayed time and the per-plan amounts change by version and over time, so always confirm the numbers in the live official view (/usage or Settings → Usage).
The usage limit is two stories tall
— hitting just one of them stops you
Claude Code and the Claude apps (web/desktop) share the same plan allowance.
Gauge numbers are illustrative. Check your real balance with /usage and Settings → Usage.
1. What this message is telling you
A typical message looks like this (wording varies by version, so treat it as a shape): "Claude usage limit reached. Your limit will reset at [time] ([timezone])." The meaning is simple: "You have used up what your plan allows for this period. It recovers at [time]." The timezone is your local setting.
The key point is that this is by design, not a malfunction. Claude's Pro / Max plans are not "unlimited" — there is a cap on usage per time window and per week. And Claude Code (CLI) and the Claude apps (web/desktop) share the same plan allowance — the official help states that "all activity in both tools counts against the same usage limits." So it is perfectly normal that "I used chat AND ran Claude Code, and together they ran out faster."
One more thing to know: there are two kinds of cap — "5-hour" and "weekly." If the reset at shown is a few hours away, you hit the 5-hour window; if it is days away, you hit the weekly window. Which one you hit changes both your wait and your options. The next section covers the structure.
2. The two-tier limit — 5-hour + weekly (+ Opus cap)
In August 2025, Anthropic added weekly usage limits to Pro / Max on top of the existing 5-hour window (driven by heavy users running it continuously). As a result, today's subscription limit is two stories tall.
The two windows act independently
Plans differ by a "multiplier" on the same structure: Pro < Max 5x < Max 20x.
The exact weekly hours get revised over time. Do not memorize fixed numbers — read the live values in Settings → Usage.
As an original (August 2025) guide, Anthropic gave rough estimates like "Pro: ~40-80 hours of Sonnet per week" and "Max 20x: ~240-480 hours of Sonnet + ~24-40 hours of Opus per week." However, Anthropic has since largely stopped publishing fixed hour figures, and the limits have been revised repeatedly (even in 2026, increases to the 5-hour window were reported). So treat those numbers as "estimates from back then," and always confirm your current allowance in the official usage view. This article deliberately avoids asserting specific current values.
3. What burns through your allowance
"It ran out faster than I expected" almost always comes down to these four, ordered by impact.
| Driver | Why it burns the allowance | What helps |
|---|---|---|
| 1) Model choice (biggest) | Opus consumes far more than Sonnet/Haiku. The docs say plainly that Opus "uses significantly more quota." On Max it even has its own weekly cap | Use /model to run routine work on Sonnet/Haiku; reserve Opus for hard problems |
| 2) Context size | Every turn reprocesses the whole conversation + attached files + tool defs + history. Bigger = more per turn | /compact, /clear, attach fewer files, smaller CLAUDE.md |
| 3) Long, continuous sessions | Always-on, endless loops. The weekly cap specifically targets this pattern | Break up work with /clear; stop unneeded auto-loops |
| 4) Subagents / MCP | Parallel fan-out and MCP servers add tool definitions and tool-call traffic | Trim active MCP servers. /usage shows a per-MCP/subagent breakdown |
In short, the heavier the model, the bigger the context, the longer and more parallel the run, the faster the allowance melts. Conversely, deliberately lowering these four makes the same plan last noticeably longer. For overall optimization see AI coding cost optimization, and for concrete token-saving tactics see Claude Code token saving.
4. Five ways to keep working now
Five moves for the moment you hit the cap, by situation. Which one you pick depends on "can you wait?" and "which window did you hit?"
When you hit the cap
/model to Sonnet/Haiku. If only the Opus cap is spent, this often lets you continue immediately./compact / /clear to spend less per turn and stretch what little remains.reset at and do other work meanwhile.On a deadline? D.
A 5-hour window comes back if you wait, so ride it out with A/B/C. If the weekly cap is gone too, D (API) or E is the realistic answer.
Knowing the API switch (D) as an "escape hatch" is powerful. Unlike the subscription's time-window lockout, the API has per-minute throughput limits but never "locks you out for a week" (you pay for what you use). See What is an AI API. Note that Pro / Max users can also enable "usage credits" to keep going past the included allowance at standard API rates (explicit consent required).
5. How to see what is left
If you can see "how much is left," you can avoid hitting the cap entirely. Three ways to check.
1) Claude Code's /usage: shows current 5-hour window consumption and weekly-window status per model. A 2026 update added a breakdown by skill / subagent / plugin / MCP server. /status also surfaces your allocation. 2) Web/desktop app: Settings → Usage shows your plan, remaining usage, and the weekly reset date. 3) API users: the Console Usage / Limits pages and the anthropic-ratelimit-* response headers. /cost (for API-key users) and /context track spend and context size.
A habit that pays off
Run /usage once before heavy work to know your balance and reset date. In a week where your weekly cap is running low, build around Sonnet from the start so you keep Opus headroom for when it matters.
6. Subscription limits vs API limits
They are easy to confuse, but the subscription (Pro/Max) limits and the API limits are entirely different systems. Knowing the difference makes the switch decision fast when it counts.
| Aspect | Subscription (Pro / Max) | API (pay-as-you-go) |
|---|---|---|
| Unit of limit | Total per time window (5-hour + weekly) | Per-minute throughput (RPM / input + output tokens per minute) |
| When you hit it | Locked out until reset | Returns 429; wait the retry-after seconds and continue (no weekly lockout) |
| How to raise it | Upgrade plan, buy credits | Tiers 1-4 unlock automatically by cumulative spend |
| Best for | Personal chat, day-to-day coding | Automation you cannot stop, large batches |
The point: the subscription locks you out by time, while the API only throttles per-minute flow and has no weekly lockout. So for deadline work you truly cannot stop, switching to an API key is the standard move. The API rate-limit details (429, retry-after, tiers) deserve their own write-up, but keep this in mind as the realistic escape hatch when the subscription runs dry.
7. Prevention checklist
An operating checklist to stop "running out when it matters."
(1) Default to Sonnet and switch to Opus with /model only for the hard parts (preserve the Opus weekly cap). (2) Keep context light with frequent /compact / /clear. (3) Check your balance and reset date with /usage before heavy work. (4) Trim unneeded MCP and auto-loops; attach only the files you need. (5) On deadline days, have pay-as-you-go API ready (so you do not stall when the subscription runs out). (6) If you are chronically short, consider upgrading the plan or moving that workload to the API.
Summary
Claude Code's "Claude usage limit reached" is not an error — it is how the Pro/Max subscription usage limits work. The limit is two stories: a "rolling 5-hour window" + a "weekly window," and Max also has a separate weekly cap for Opus. Because Claude Code and the Claude apps share the same plan allowance, they can run out faster together. If the reset at is hours away it is the 5-hour window; days away, the weekly window.
The biggest consumer is model choice (Opus is the largest), then context size, long continuous runs, and subagents/MCP. When you hit the cap: A: drop the model -> B: trim context -> C: wait for reset, and if you cannot wait, D: switch to pay-as-you-go API / E: more allowance or upgrade. See your balance with /usage and Settings -> Usage. And since the exact numbers get revised over time, do not memorize them — confirm in the live official view. Related: token saving and extra costs, Opus/Sonnet/Haiku pricing, Claude Code error roundup.
FAQ
Q. Is "usage limit reached" a bug? I am paying for this.
A. It is by design, not a bug. Pro / Max are not "unlimited" — there are usage caps per 5-hour window and per week. Even as a paying user, once you exceed what that window allows, you are paused temporarily; it recovers at the reset at time shown. Note that Claude Code and the Claude apps share the same allowance, so using both drains it faster.
Q. When does it reset? It said "reset at 3pm."
A. That is the reset time for the 5-hour window (your local time); a few hours and it recovers. If instead it shows "days away," you hit the weekly window, and you can find the next weekly reset date under Settings → Usage. If even the weekly cap is gone, your options are to wait, switch to pay-as-you-go API, or upgrade.
Q. Why do I hit the limit so fast?
A. The biggest factor is model choice. Opus burns through the allowance far faster than Sonnet, and on Max it has a separate weekly cap that drains first. On top of that, large context, long continuous runs, and heavy use of subagents or MCP push consumption up. Dropping routine work to Sonnet with /model and trimming context with /compact alone makes a big difference.
Q. How do I keep going right now without waiting?
A. (1) /model to drop to Sonnet/Haiku (works when only the Opus cap is spent), (2) switch to a pay-as-you-go API key (no weekly lockout), (3) enable usage credits (continue past the included allowance at standard API rates), (4) upgrade your plan (Pro to Max). For deadline work, having pay-as-you-go API ready in advance is the safe play.
Q. Can I check how much I have left?
A. Yes. In Claude Code, use /usage (shows the 5-hour and weekly windows per model, plus a per-MCP/subagent breakdown) and /status. In the web/desktop app, Settings → Usage shows your plan, remaining usage, and the weekly reset date. Checking once before heavy work lets you avoid hitting the cap.
