Unknown Unknowns: Should I Actually Pay for Fable 5

If you've been enjoying the free ride on Anthropic's latest mega-model, it's time to wake up. Especially for those who tend to run everything on auto-mode, pay close attention, because some heavy usage $$$ is heading your way. Starting the 12th of July (was actually supposed to be today!), Fable 5 will no longer be included in your regular Claude subscription.

From here on out, it is strictly pay-as-you-go. At twice the price of Opus, your automated scripts are about to get very expensive if you don't check your settings.

But if it's better, it's worth it, right?

Well, maybe.

This is the point where you should really understand the differences between the models because they are no longer trivial.

Claude Opus 4.8 is an excellent execution engine, and there is no argument on that. For the past months I've been using it to execute whole epics, perform complex git rebases, and plan evaluation sets. It excels at routine feature work, debugging, and even implementing those AI-generated pull request reviews where you need fast and focused responses. If the task is bounded, Opus handles it perfectly fine. More than fine. It excels. But still, there are some areas where I was left with a longing for something more.

And this is the real place where Fable shines. It gives you more. It feels like it can do autonomous engineering, like a senior architect. You ask it to do less and it gives you more: insight, fewer manual revisions, magic. And it's not even slow.

The catch is of course the price. It costs $10/M input and $50/M output tokens, exactly double the price of Opus. So as the dealer gave me the candy for free, I got used to it, but I'm not going to keep paying just because I got hooked.

How I'm going to use it

The first thing I'm doing is switching back the default to Opus.

Paying double the context cost to have a mega-model refactor a basic repository structure is just a great way to optimize Anthropic's revenue, not my codebases.

From now on, I'll be using Fable in planning flows, running my BMADs, and doing architecture spikes. I trust it to find the "unknown unknowns"—the blind spots in your project logic before you spend a week executing against a broken premise. Once I have my spec and task context done, I'll be switching back to Opus and let it run and build what the big boss (Fable :-D) has come up with.

So before you wrap up your day, do yourself a favor: check your config files tonight, adjust your routing scripts, and keep an eye on the meter tomorrow.

BTW: Keep in mind that Fable 5 comes with a mandatory 30-day data retention policy, unlike Opus which supports zero data retention. If you have strict data compliance requirements, that alone might make the choice for you.