[Feature Request] Keep Claude Fable 5 included in the Max plan after July 7 (not usage-credits-only)

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)

1. Keep the current 50%-of-weekly-limit inclusion for Max beyond July 7.
2. A reduced included cap for Max (e.g. 20–25% of weekly limits), with credits only beyond that.
3. 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.