[Feature Request] Keep Claude Fable 5 included in the Max plan after July 7 (not usage-credits-only)
Status Open
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 9 comments · opened Jul 2, 2026
Request
Please keep Claude Fable 5 included in the Max plan (within plan usage limits) after July 7, 2026, instead of moving it to usage-credits-only.
Context
- At launch, Fable 5 was included on Pro/Max/Team/Enterprise plans through June 22, and after the July 1 redeployment it is included for up to 50% of weekly usage limits through July 7 (per https://www.anthropic.com/news/redeploying-fable-5).
- After July 7, subscribers must buy separate usage credits at roughly API rates ($10/$50 per MTok) to use Fable 5 at all.
- The original announcement (https://www.anthropic.com/news/claude-fable-5-mythos-5) said Anthropic plans to "restore Fable 5 as a standard part of subscription plans" once capacity allows — this request is to prioritize that restoration for Max, or share a timeline.
Why Max specifically
- Max ($100–$200/mo) exists precisely for users who want the most capable model as their daily driver; Fable 5 being credits-only makes the top-tier subscription no longer include the top-tier model.
- A capped inclusion (e.g. the current 50%-of-weekly-limit model, or a lower cap like 20–25%) would let Max users keep using Fable 5 for the hardest tasks while still managing capacity, with credits as overflow beyond the cap.
- Credits-on-top-of-subscription at full API rates is a significant effective price increase for workflows that were built around Fable 5 during the launch window.
Suggested options (any of these would help)
- Keep the current 50%-of-weekly-limit inclusion for Max beyond July 7.
- A reduced included cap for Max (e.g. 20–25% of weekly limits), with credits only beyond that.
- A published timeline/criteria for when Fable 5 returns as "a standard part of subscription plans" as stated in the launch announcement.
Thanks — Fable 5 has been a step change for long-horizon agentic work in Claude Code, and predictable access to it is the main reason to stay on Max.
9 Comments
Totally agree
agreed
agreed this is not a good look
Agreed. I have turned off the renewal of my Max plan. I cannot justify $200/month without Fable included. There are too many other competitive options at that price point.
I would definitely support this. User experience and long-term trust from user community can be vital for business success. Market share is also vital in keeping the wheel running faster than competitors. But I suppose you guys might already think about this and agree on it. You just wanted the process to be much more fun ;-p
As a Max subscriber I build real work around the model that ships as my default, and moving Fable 5 to usage-credits-only after July 7 pulls that out from under paying subscribers with no committed return date. I understand the capacity constraint, but "as soon as capacity allows" isn't something I can plan around. Please prioritise restoring Fable 5 to standard Max inclusion, and in the meantime give subscribers a concrete timeline or interim allowance rather than an open-ended metered-only period.
+1. The main reason to pay for a top tier plan is getting the most capable model as a daily driver. Moving Fable 5 to usage-credits-only means the top subscription no longer includes the top model.
I get that capacity is the real constraint, and I appreciate the stated commitment to restore Fable 5 to subscriptions once capacity allows. Two asks: prioritize that restoration, and in the meantime offer a capped inclusion (say 20 to 25% of weekly limits, credits as overflow) instead of nothing. A published timeline or set of criteria would also help, since “when capacity allows” is open-ended. Thanks for considering.
Adding my profile to this thread because I'm the customer this decision is aimed at, and I want the data point on record.
I'm a Max subscriber who runs near my weekly limits most weeks. Separately, I spend roughly $20/day in API usage on Haiku and Sonnet running production automation across four businesses I operate. I am not a casual user and I am not price-insensitive. I pay Anthropic several hundred dollars a month, every month, by choice.
Here's my experience of the last month as a paying customer:
The capability difference between Fable and Opus is not marginal for my work. Fable's intent inference and long-horizon reasoning save me real development time in ways Opus does not replicate. I've used both extensively. Telling heavy users "Opus is fine" is not responsive to why we bought Max in the first place: predictable access to the most capable model.
I understand the unit economics. Flat-rate plans can't subsidize unbounded frontier usage. But the sequence here, launch it bundled, let workflows form, then meter it with days of notice and vague timelines, is a trust problem independent of the economics. "When capacity allows" with no criteria and no date is not a commitment, it's a deferral.
What would keep my money here:
Absent one of those, the math changes. A competitor now bundles its frontier model into a $20 plan. I have reasons I'd prefer not to use them, but preference has a price, and this decision is testing it. I'd rather stay. Give me a reason that isn't "trust us."
Your point about “credits on top of the subscription” being an effective price increase is important—the sticker price alone no longer describes the deal, especially when predictable access is the reason to stay on Max.
I operate PricingTrace, an independent source-linked pricing and subscription-terms tracker. Claude already has a page here: https://pricingtrace.com/tools/claude
It won't change Anthropic's product decision, but the page preserves the current baseline and lets you create a free alert for meaningful pricing, usage-limit, or terms changes. Disclosure: this is my own project, and the alert is free during validation.