Update, July 2
The practical update is that Fable is back, but the meter matters.
Anthropic says Fable is included for up to 50% of weekly limits on Pro, Max, Team, and select Enterprise plans through July 7. After that, Fable access moves to usage credits. Separately, the ClaudeDevs account posted that 5-hour and weekly limits were reset after the relaunch, which Digg and user threads quickly amplified because people were already burning through quota.
The forum version is rougher: some users are happy about the reset, some are frustrated by the 50% cap, and others are watching whether safety reroutes to Opus 4.8 make Fable feel changed in normal coding work. Treat that as field noise, not a spec. The spec is the Anthropic post.
What changed
- U.S. export-control restrictions were lifted and Anthropic redeployed Fable 5.
- Anthropic says Pro, Max, Team, and select Enterprise plans get Fable included for up to 50% of weekly usage limits through July 7, then it moves to usage credits.
- Anthropic says blocked Fable requests are sent to Opus 4.8, and the new classifier can flag benign coding and debugging requests more often.
- The ClaudeDevs account announced a reset of 5-hour and weekly limits after the relaunch. Digg picked up the same reset thread and the comments around Fable burning through quotas quickly.
What to check now
- If your stack routes by model, re-run a live availability check before resuming normal routing.
- Confirm how your current account handles the 50% weekly allowance, usage credits, and any reset window.
- Watch for classifier reroutes: a request that starts as Fable may finish as Opus 4.8 if the safeguard trips.
- Keep a fallback branch for when phased rollout gates move.
The chatter layer
This part is hearsay and forum signal, not confirmed platform policy.
Digg's linked story frames the reset as a make-good after users burned through limits quickly once Fable returned. The embedded X chatter is mostly celebratory, but the pattern is the useful bit: people were not just talking about availability, they were talking about quota burn.
Hacker News and Reddit threads are circling the same questions: whether a one-week 50% allowance is generous or just a narrow promotional window, whether the new classifier makes Fable feel different, and whether the Opus reroute is a quality issue, a billing issue, or both.
One independent write-up calls the relaunch a "permission tier" problem: Fable is back, but access is now metered, rerouted, and policy-shaped in a way users can feel during normal work. That is an interpretation, not an official claim, but it matches the public anxiety around resets and limits.