Claude Has Two Meters. The 20x Is Only on One.
On August 29, Anthropic announced that Claude Code's weekly limits would be permanently raised by 25% on September 14, and then, in the same thread, that this works out to a 17% reduction compared to today. Both sentences are true. They are true for the same reason the Max 20x plan can feel like a 2x plan by Thursday: Claude does not have one usage limit, it has two, and the multiplier you pay for is printed on only one of them. This is the arithmetic of both meters, what drains each, where the numbers on the pricing page stop, and what to do about the week you cannot see.
The meter with the multiplier on it
Start with the sentence Anthropic prints on its own pricing page, in the FAQ under "What are the usage limits on each plan": "Every plan has usage limits that reset on a rolling five-hour session window, and paid plans add weekly limits on top." Two meters, one sentence, and the order matters. The five-hour meter is the primary one. It is where every headline number is defined: "Pro gives you at least 5x more usage per 5-hour session than Free. Max gives you 5x or 20x more usage per 5-hour session than Pro."
Read that again with the unit attached. The 20x is a multiplier per five-hour session. It is not a multiplier on your week, your month, or on any number that appears on a bill. If Pro's five-hour budget is one unit, Max 5x is five units every five hours and Max 20x is twenty. That is the whole published contract for the number on the checkout page.
The meter is also shared. "Your activity across Claude on web, desktop, mobile, and Claude Code all draws from the same pool." A chat in the app, a Cowork session, and a Claude Code run in the terminal drain the same five hours. There is no fixed message count, because "how much you can do depends on the length and complexity of your conversations, the model you choose, and the features you use."
The meter with the discretion on it
The second meter sits on top and has a different legal texture. The same FAQ: "To manage capacity and make sure all users have fair access, we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion." No multiplier, no ratio to the five-hour meter, no published size. The plan comparison table on that page adds one hard fact: on both Max tiers, the Fable model line reads "50% of weekly limits". So the weekly meter exists, it is smaller than you would guess from the five-hour meter, and the most expensive model is capped at half of it.
This is the gap the whole summer's argument fell into. People bought a 20x and expected the week to be 20x. The week was never priced. The only weekly numbers that ever appeared in public were ranges of Sonnet hours in a 2025 plan guide, and those, as one widely shared thread pointed out on August 31, put the $200 plan at roughly 1.7 times the weekly hours of the $100 plan. I could not find that guide on the current site, so treat the 1.7 as reported. The class action filed in June, Kahn v. Anthropic PBC (3:26-cv-05763, N.D. Cal.), makes the same argument in legal form: that the 5x and 20x figures describe one window while the binding constraint is another. Anthropic moved to dismiss the amended complaint on August 19; the hearing is set for November 6. Nothing is decided.
Pick a plan, set how fast you burn, and watch both meters. The five-hour meter refills. The weekly meter does not until the week ends.
Units: one Pro five-hour budget = 100. The 5x and 20x multipliers apply to this meter per the pricing FAQ. The weekly meter is modeled as a multiple of the five-hour budget; the 15% default is one Max 20x user's estimate on Hacker News, not an Anthropic number. The demo resets the session meter every five hours; the real window is rolling.
What actually drains them
Both meters are fed by the same stream of tokens, weighted by model. Anthropic's usage-limit guidance lists the levers: message length, attachment size, conversation length, tool use such as Research and web search, model choice, effort level, artifact creation. Every one of those is a token count or a token multiplier.
Claude Code makes the mechanism visible because it is the least conversational surface. Per the Claude Code usage article, every turn sends three things: the full conversation history, the project context (CLAUDE.md, files read), and the new prompt. History is called out as the fastest-growing consumer. That is why a long session gets more expensive per turn even when your prompts stay short, and why /clear and /compact exist. If you have read Inside the Claude Code Harness, you know the harness is built to preserve the prompt cache; a cache miss re-reads the whole prefix at full price on the API, and on a subscription it shows up as a meter that moved more than you expected.
Two things multiply the stream without you typing more. Effort level trades output tokens for quality; the higher tiers think longer. And subagents fan out: one Max 20x subscriber on Hacker News described five research agents spinning up 26 subagents and burning "the remainder of my weekly in the span of 20 minutes". The same commenter estimated the five-hour budget at "about 15% of the weekly on Max 20x", which is where Fig. 1's default ratio comes from. One person's estimate, but it is the only one anyone has offered with a number attached.
The arithmetic of September 14
Now the announcement. On August 29, the Claude Developers account posted: "Starting September 14, we're permanently raising standard weekly limits in Claude Code by 25% for Pro, Max, Team, and seat-based Enterprise plans. Until then, the current 50% increase will be in place." Then, in the same thread as reproduced by BleepingComputer and by commenters on Hacker News: "Compared to today, this works out to a 17% reduction in weekly limits on Claude Code." BleepingComputer reports the original thread was deleted and re-posted with that clarification.
The two numbers reconcile once you know the history of the weekly meter, which is short. On May 6 Anthropic doubled Claude Code's five-hour limits for Pro, Max, Team and seat-based Enterprise, removed the peak-hours reduction, and tied both to new capacity from a SpaceX Colossus 1 deal. That was the five-hour meter. A week later, on May 13, the weekly meter got a separate, explicitly temporary boost: a 50% increase to weekly usage limits in Claude Code, applied automatically, and, in the article's own words, "5-hour usage limits are not affected by this promotion". The promotion was first scheduled to end August 19, then extended to August 31, and the live article now says September 13.
So the ladder is: standard 100, boosted 150 since May, and 125 from September 14. Against the standard, plus 25%. Against what you have been using since May, 125 divided by 150 is 0.833, a 17% cut. Both true. Which one you feel depends on which one you planned around, and most people planned around the meter they could see.
Slide the standard allowance. The two comparisons in the announcement are both true, and they point in opposite directions.
Dates and percentages from the Claude Code weekly limits promotion article and the August 29 announcement. The bars are proportional to the slider; the ratios do not depend on it.
One more line has been circulating, quoted in Theo Browne's post and attributed to the same announcement: that on September 14 "we will be removing the separate weekly limit for Fable, so you will now be able to use your full limit with your preferred Claude model." That would retire the "50% of weekly limits" line for Max. As of September 3 the support article does not say it, so file it as reported until the pricing table changes.
Pricing the meter you can see
Here is the arithmetic the "Save 50%" badge on the Max checkout invites, done honestly. Pro is $20 a month ($17 on annual). Max is "from $100" for the 5x tier and $200 for the 20x. On the five-hour meter, Pro buys one unit, Max 5x five, Max 20x twenty. Dollars per five-hour unit: $20, $20, $10. On that meter the 20x plan really is half price per unit, and the badge is honest.
Move to the weekly meter and the column goes blank, because nobody has published the weekly sizes. Users fill the blank with reports. A recurring one on r/ClaudeCode and r/ClaudeAI is that the 20x plan gives about twice the weekly usage of the 5x plan, which would make the two tiers the same price per weekly unit. The 2025 hours ranges quoted above imply about 1.7x, which would make the 20x plan more expensive per weekly unit. The lawsuit's complaint, as reported by secondary coverage, alleges 3.5x for the 5x plan and 6 to 8x for the 20x plan against Pro. None of these is an Anthropic number. Fig. 3 lets you pick the ratio and see what the badge means under each.
The multiplier you pay for is printed on the five-hour meter. Price it there, then try to price it on the weekly one.
| plan | price / month | five-hour units | $ per five-hour unit | weekly units (Max 5x = 1.0) | $ per weekly unit |
|---|---|---|---|---|---|
| Pro | $20 | 1 | $20.00 | not published | ? |
| Max 5x | $100 | 5 | $20.00 | 1.0 | $100.00 |
| Max 20x | $200 | 20 | $10.00 | 2.0 | $100.00 |
Prices from claude.com/pricing on September 3, 2026, monthly billing. The five-hour units are the published multipliers. The weekly ratio is a user report, not a published figure; the slider covers the range people have claimed.
When the meter drains and you did nothing
There is a third way to lose a week that has nothing to do with plans. On August 30 Anthropic began emailing users whose accounts had been used by someone else, and the wording is worth keeping: "If your usage limits looked like they refilled and then drained while you weren't using Claude, this was likely the cause." Per BleepingComputer's report, general-purpose infostealers (Vidar, LummaC2, StealC, RedLine, Acreed on Windows, Atomic Stealer on a few Macs) were lifting authenticated Claude browser sessions along with everything else on the machine, and "a bad actor has now started picking the Claude sessions out of what it collected and using them." A stolen session skips the password and the second factor. Anthropic is signing affected users out, removing saved payment methods, and refunding charges it identifies as unauthorized.
The mechanism matters for the meter argument because a subscription meter is a shared pool with no per-session accounting you can see. If your weekly drained on a day you were away, the first suspect is not Anthropic's arithmetic. Sign out everywhere, then look at the machine.
Reading both meters from the terminal
The tooling has been catching up with the two-meter reality all month, and the Claude Code changelog is the record. Version 2.1.234 in mid-August added the line most people wanted: "Claude Code now continues your session automatically when a claude.ai usage limit resets; turn it off in /config." That does nothing to the caps, but it turns the five-hour wall from an interruption into a pause. The status line's rate_limits field exposes both windows, five-hour and seven-day, with a used percentage and a reset time each, and the Settings usage tab shows the same pair. Version 2.1.251 on August 28 added a per-session prompt-cache line to /cost: hit ratio, misses, tokens re-cached, warm or cold. That is the number that explains a session which drained faster than its prompts suggest.
The desktop app went the other way for a day. On August 31 a GitHub issue reported that the small circle next to the composer, which used to show the conversation's context window, had silently changed meaning and now tracked plan usage against the five-hour limit. People ran /compact and watched the circle not move. Two meters, one indicator; the same confusion this essay is about, drawn as a UI bug.
What to do with two meters
Treat the weekly meter as the budget and the five-hour meter as the throttle. The throttle refills; the budget does not, and it is the one nobody will quote you a size for. Plan the week, not the session.
Know which wall you hit. The five-hour wall pauses you; with auto-continue on, it barely does. The weekly wall stops you until reset, and no plan upgrade changes the ratio between them that you have not been told.
Spend tokens where they compound. Effort tiers and subagent fan-out are the two multipliers that can empty a week in an afternoon; the Hacker News example above was 26 subagents in 20 minutes. Read /cost after a long session and look at the cache line before blaming the model.
And when Anthropic says "more visibility and control of your usage" is coming, which the August 29 clarification promised, the useful version is simple: put a size on the second meter. Until then, the number you are paying for is the one on the throttle, and the essay you want next is about what happened when a faster model met that throttle two days later.
Keep reading