First Days with Fable 5: How Fast the Allowance Goes, and Splitting Specs from Implementation

The first thing that surprised me about actually using Claude’s Fable 5 was how casually you can use it. Alongside the capability everyone was describing, I got a feel for how the allowance goes and how to divide the work. Here is what the first few days taught me.

Conversation costs less than you would think

Worried about the allowance, I started cautiously — preparing the material to feed it on a different model (Opus 4.8), using a little, checking the balance, using a little more.

The conclusion: conversation costs very little and there is no need to be nervous about it. What consumes tokens heavily is work like writing code. Be relaxed about talking, careful about implementing, is how the consumption actually feels.

Specs on Fable 5, implementation on familiar tools

Handing implementation to Fable 5 as well would presumably be smarter still, but for my projects the ordinary models (Opus 4.8, GPT-5.5) were enough. So I split it: everything up to the specification on Fable 5, implementation on Codex, which I know. The idea was to concentrate a scarce allowance on the thinking.

Opus 4.8, which I was using for the first time, turned out to be better than expected, and implementing through Claude Code was comfortable. That deserves its own article, which follows later.

The moment it landed: a problem I had given up on

What made Fable 5’s capability real to me was a video editing problem I had been stuck on for a long time. The sequence went:

• Have Opus 4.8 write up everything I had tried, how far each attempt got, and what failed
• Give that document to Fable 5 and ask for an approach and a system
• Take the resulting system back to Opus 4.8 and resume the work

The problem that had resisted for so long came apart quickly. More importantly, the system Fable 5 built could be run on ordinary models afterward.

Have the capable model build the system

The value of a top-tier model lies less in doing the work in front of you than in building something you can keep using. Once the system exists, day-to-day operation runs on your usual model. If you have a limited window with Fable 5 and are unsure what to spend it on, put it into resolving what you have been stuck on, and into building assets.

This article is adapted for AI Jiten from testing notes originally published on the author’s blog, Delaymania.