Skip to content
Dustin's AI Lab
Go back
Updated:

When to Call In Fable: Three Moments, and Don't Turn On ultracode

The most expensive model is not meant to run the whole way. Three moments where calling in Fable feels right to me, plus why I cap Opus 5 at med, and the weekly cycle I fell into: efficiency king Monday to Thursday, Fable mode Friday to Sunday.

On this page
  1. Postscript: It Turned Into Two Modes a Week
  2. Postscript: Two Ways to Mix Models

When do I call in Fable? The three moments that work best for me:

  1. The main agent uses Fable for overall architecture planning, subagents do the implementation, and then it comes back to Fable for sign-off. (This is also the one most people recommend.)

  2. The main agent runs on Opus or Sonnet, and when it gets stuck partway through, or I want an adversarial review or the thinking pushed wider, I call in a single Fable subagent as a one-off consultant. (This is the one I ended up using more.)

  3. The weekly reset is tomorrow and there’s still a pile of quota left. (A\ isn’t getting one bit of that for free.)

Someone asked me the other day whether to turn on ultracode.

Why turn on ultracode (? Want to enjoy the feeling of ten thousand horses charging? Never mind that ultracode’s xhigh mode has an overthink problem on Opus 5. It wrestles with itself in its own head and just burns your tokens.

Turn ultracode off. Cap Opus 5 at med. Most subagents are fine on Sonnet. What matters is being clear about which point the smart model joins at: planning, coordination, on-call consultant, or sign-off.

Postscript: It Turned Into Two Modes a Week

This is funny. I’ve realized I’ve quietly turned into this:

Monday to Thursday: efficiency king, routine work running at full tilt (Sonnet plus the skills and pipelines I’ve already built, local models, 5.6 Luna/Gemini routing, and overnight automation on top).

Friday to Sunday: I suddenly notice I’ve been way too frugal the past few days and there’s a pile of quota left, so I open Fable and turn into creativity-explosion visionary mode, doing long-range exploration and planning for the future, tuning the harness, setting the guardrails.

Sunday 5pm: back to cowardly mode, and the cycle starts over.

A phone usage panel: 92% of the current session used, 97% of the weekly all-models limit used, and only 47% of the Fable-only limit

So my clients all reach me Monday to Thursday, and the new deliverables all ship Friday to Sunday.

Are you the same as me?

Postscript: Two Ways to Mix Models

Switching models means a cache miss, so the usual move is a subagent. When the path isn’t clear yet, run a smart main agent and hand the grunt work to cheap throwaway subagents. When the path is clear and only a few hard spots remain, flip it: cheap main agent, and call in a smart subagent as a one-off consultant or for sign-off.


15-Minute AI Adoption Diagnosis

Fill in a short form to book your free 1-on-1 diagnosis, and find out how you can work with AI without the pain and get a real productivity lift.

Book my free diagnosis
Share this post on:
Previous Post
The Week of Qwen 3.8 Open Weights: From Model Card to A3B Getting Deleted
Next Post
Your Own Machine Is the Attack Surface: Leftover Credentials, Permission Flags, Untrusted Input