Anthropic just redeployed Claude Fable 5 — the most capable model they have ever released — and right now it's included on the Pro or Max plan you already pay for. That window closes on July 7, 2026. After that, using it costs usage credits per token.
This is the how-to from the video: don't spend the free window chatting. Point Fable 5 at real work. Below are the three exact prompts, copy-paste ready.
Why this matters right now
Fable 5 sits above the Opus class. On Anthropic's own launch, Stripe pointed it at a 50-million-line codebase and it did a full migration in one day — work that had taken their team two months by hand. It one-shots things that used to take a hundred back-and-forth prompts.
The catch is the calendar. Here is the access timeline, straight from Anthropic:
| When | Fable 5 access | Cost to you |
|---|---|---|
| Now → July 7 | Included on Pro / Max / Team (up to 50% of your weekly limit) | Free — already in your plan |
| After July 7 | Usage credits only | $10 / 1M input, $50 / 1M output |
So the move is simple: in the next few days, aim it at the hard thing you've been avoiding.
The full step-by-step
1. Open Claude (web, desktop, or Claude Code) and make sure the model picker is set to Fable 5.
2. Pick the one task you keep putting off — a messy folder, a slow script, or a giant project you can't hold in your head.
3. Paste the matching prompt below and let Fable 5 do the heavy lifting. Review its plan before it changes anything.
4. Do this before July 7 while it's free on your plan.
The exact prompts
1. Clean up a messy folder
Go through this folder. Tell me what's junk, what's duplicated,
what's misfiled, and what's actually important. Then propose a
clean structure and, once I approve, reorganize it — moving and
renaming files so a stranger could find anything in 10 seconds.
Show me the plan before you touch anything.
Fable holds the whole folder in context at once and reasons about what belongs where — not just pattern-matching filenames.
2. Make a slow script faster
Profile this script and find the slowest parts. Rewrite the hot
path to be as fast as possible without changing behavior. Show me
a before/after timing and explain each change in one line. Keep it
readable — no clever tricks I can't maintain.
It spots the bottleneck most models miss, and it explains the fix instead of hiding it.
3. Save your whole project into one memory file
Read this entire project. Write ONE markdown memory file that
captures everything you'd need to continue tomorrow with zero
context loss: what this is, the architecture, key decisions and
why, what's done, what's next, and the gotchas. Write it so a
fresh instance of you could pick up exactly where we are.
This is the highest-leverage one. Fable stays coherent across millions of tokens and improves its own notes, so a single memory file becomes the thing that lets you (or a fresh session) resume instantly.
Tools & links
- Claude Fable 5: the model itself — set your picker to it. claude.ai
- Anthropic's launch post: the source for pricing, the Stripe proof, and the plan timeline. Claude Fable 5 and Mythos 5
- Redeploy details (the July 7 date): Redeploying Fable 5
- Manage usage credits (what kicks in after July 7): support.claude.com
What most people get wrong
They treat the best model on Earth like a chatbot — asking it trivia and quick rewrites. That wastes the one thing Fable is uniquely good at: long, hard, multi-step work you'd normally avoid. The fix is to hand it your worst task, not your easiest one. The migration, the refactor, the project you can't hold in your head — that's where it earns the premium.
One step to take today
Open Claude, switch to Fable 5, and run prompt #3 on your current project. You'll have a memory file that pays off every session after — and you'll have used the free window before it closes on the 7th.