TL;DR (June 2026): Claude Fable 5 is included in Pro, Max, Team, and seat-based Enterprise plans free from June 9 through June 22, but it counts roughly double the usage of Opus toward your plan limits, so every Fable 5 session drains your allowance about twice as fast as the same work on Opus 4.8. On June 23 it leaves plan limits entirely: continued use bills against prepaid usage credits at full API rates ($10/$50 per million tokens, capped at $2,000 of redemption per day). Reddit's r/ClaudeAI is at war over it, an 841-upvote thread titled "Claude's new usage limits are insane" and Max 20x users reporting they burn 2% of their allowance per minute. This page is the math: what actually counts, how fast each plan really drains, and the six moves that stretch a subscription through the squeeze.
Anthropic shipped its best model and its most confusing meter in the same launch. Fable 5 arrived June 9 to genuinely rapturous reviews, and within 48 hours the loudest thread on r/ClaudeAI was not about capability, it was titled "Claude's new usage limits are insane" (841 upvotes, 279 comments), flanked by "Fable 5 is insanely good, but watch your usage, I was burning 2% a minute on 20x" (220 upvotes) and "Anyone else feel like Claude is missing a middle-tier plan?" The complaints are not irrational, and they are not really about the limits. They are about a weighting rule most subscribers never read. Here is the rule, the arithmetic, and the playbook.
The three-phase structure nobody read
| Phase | Dates | What Fable 5 costs you |
|---|---|---|
| Free window | June 9 to June 22 | No extra charge on Pro/Max/Team/Enterprise, but each Fable 5 token counts ~2x an Opus token against your plan allowance |
| The cliff | June 23 | Fable 5 is removed from plan limits entirely. Plan usage no longer covers it at any weighting |
| Usage credits | June 23 onward | Prepaid credits billed at standard API rates: $10/M input, $50/M output, bought in Settings > Usage (web only), max $2,000 redeemed per day, optional auto-reload |
Anthropic's stated intent is to restore Fable 5 to subscription plans "once capacity allows," which is a real promise with no date attached. Until that date exists, the operative planning assumption is the table above.
Why your Max plan suddenly feels small
The 2x weighting is the whole story of the Reddit anger, and it compounds with a behavioral trap: Fable 5 is better, so people point it at bigger jobs. A Max 20x subscriber who used to run Opus 4.8 sessions comfortably inside the five-hour reset window now runs Fable 5 on the same workload and pays the double weight on a model that also tends to produce longer, more thorough outputs. The "2% per minute" report is exactly what that arithmetic predicts: a heavy agentic session on the 20x plan, weighted at 2x, with verbose frontier output, can plausibly traverse an entire five-hour allowance in under an hour. Nothing is broken. The meter is just measuring something different from what the subscriber's intuition was calibrated on.
Three mechanics determine how fast you actually drain:
- Everything shares one allowance. Chat messages, Claude Code terminal sessions, Research mode, and project file content all draw from the same plan usage, and all of it consumes credits once you are past plan limits. A big project context attached to every message is a multiplier you chose once and pay continuously.
- The reset cycle is unchanged: every five hours. The limits did not shrink; the weighting changed. If you schedule heavy Fable 5 work just after a reset and batch it, you get materially more out of the same plan than someone who trickles requests across the window.
- Claude Code is the heavy consumer. Terminal agent sessions read files, run tools, and iterate, each loop is input tokens at 2x weight. The same prompt in chat and in Claude Code can differ by an order of magnitude in tokens consumed.
The June 23 decision tree
When the free window closes, every Fable 5 user lands in one of three positions, and it is worth deciding which one you are before the cliff rather than at 9 a.m. on the 23rd:
- Drop back to Opus 4.8 by default. For most coding and analysis work, Opus 4.8 at normal plan weighting remains the rational default, and on the API it is literally half Fable 5's price ($5/$25). Reserve Fable 5 for the tasks where the capability gap is worth paying for, which is a routing decision, and routing decisions need cost-per-task data, not vibes.
- Buy usage credits deliberately, not reactively. Credits only activate after plan usage is exhausted, bill at full API rates, and redeem against a $2,000/day ceiling. The right way to use them is as a sized monthly budget for a known Fable 5 workload. The wrong way is as an emergency top-up you discover mid-task, which is how surprise-bill stories are born. Mobile subscribers note: purchase works only on the web app.
- Move the workload to the API. If your Fable 5 usage is systematic (agents, pipelines, batch jobs), subscription-plus-credits is the expensive path. Direct API access at $10/$50 with 90% prompt-caching discounts ($1/M cached input) and 50% batch pricing will usually beat credit top-ups for anything resembling production traffic, the full math is in our Fable 5 pricing breakdown.
Six moves that stretch a plan through the squeeze
- Route by task, not by loyalty. The single biggest lever. Use Fable 5 for architecture, hard debugging, and long-context synthesis; use Opus 4.8 or Sonnet for routine edits, boilerplate, and summaries. Subscribers who route deliberately report their allowance lasting 2 to 3x longer, which is exactly what un-paying the 2x weight on 70% of traffic predicts.
- Trim the always-attached context. Project files count toward usage on every message that includes them. A 100K-token project context attached to fifty messages a day is five million weighted input tokens of pure overhead. Attach what the task needs, detach when it changes.
- Batch heavy sessions to the reset clock. Five-hour resets reward concentration. One planned two-hour Fable 5 deep-work block per window beats ambient all-day usage of the same total volume, because you stop paying the weight on idle-curiosity queries.
- Watch the meter, not your gut. Settings > Usage shows the drain in real time, and the in-product warnings fire at meaningful thresholds. The Reddit threads are full of people who discovered the 2x weighting empirically, mid-task, at 0% remaining. Two scheduled glances a day prevents that genre of surprise entirely.
- Keep agentic work surgical during the window. A Fable 5 Claude Code session that explores a repo for twenty minutes is the most expensive thing you can do on a subscription right now. Scope agent tasks tightly, give them the relevant paths up front, and the same outcome costs a fraction of the tokens.
- If you manage a team, meter per developer now. Team and Enterprise admins are about to learn which engineers are Fable 5 power users the same way Copilot admins learned it on June 1: from the bill. Per-developer, per-model metering with thresholds, the pattern from the FinOps playbook, turns the June 23 transition from a surprise into a line item.
The middle-tier vacuum is the real complaint
Step back from the mechanics and the r/ClaudeAI discourse has one coherent grievance underneath the noise: there is no good seat between Pro and Max 20x for a serious individual user of a frontier model. Pro is too small for daily Fable 5 work even at 1x weighting; Max 20x is built for it but now drains at double speed; and usage credits at full API rates feel like paying retail on top of a subscription. The pattern matches the whole industry's 2026 direction, flat tiers retiring, workload classes carved out of subscriptions, metered overflow everywhere, and the direction has a simple read: the subscription is becoming the on-ramp, and the meter is becoming the product. Fable 5's three-phase rollout is that thesis executed in a single fortnight.
The honest take
Anthropic's structure here is more defensible than the outrage suggests: a genuinely free two-week frontier window is generous by 2026 standards, the 2x weighting is a real capacity constraint priced honestly, and prepaid credits with a daily ceiling cannot produce a five-figure surprise bill. What it is not is legible. The weighting rule lived in documentation while the launch post led with "included in your plan," and the gap between those two sentences is precisely the 841 upvotes. For users, the lesson is the same one every provider has taught this year: read the meter's rules before pointing the new model at your workload, because the meter's rules are the pricing now. And if you cannot see your own burn rate per model and per task, you are not actually deciding any of this, the reset clock is deciding for you.