Fable5 Opus5 5 Orchestrator

Fable Orchestrator

Run Claude Fable 5 all day — without watching the usage meter.

Fable 5 is the best chair a Claude Code session can have, and the most expensive seat in the house. Let it type every token itself and the session ends rate-limited, waiting out the reset window.

This plugin makes the split mechanical. Fable 5 keeps the chair and spends tokens on planning, arbitration and final decisions. Everything else goes to named workers: the volume — implementation, research, briefs, review, bulk reading — to Sonnet 5, and the predictably hard slices — architecture, irreversible migrations, security review — straight to Opus 5.5, which doubles as the escalation lane. The chair sizes each worker's reasoning effort to the job, low for mechanical sweeps, xhigh for architecture and security — Opus 5.5 never runs at max.

No ledger, no interview, no mandatory verification phase. Earlier versions gated the act of delegating with a requirements file and a clarification loop. Both are gone. What is left is one rule with teeth: delegation is the default, and a hook notices when the chair quietly does the work itself.

The division of labor

Your Fable limit pays for the thinking and almost nothing else:

Why this trio

- Fable tokens are the heaviest draw on your limit. Every token of bulk work kept off the chair extends how long Fable stays in it.
- Sonnet 5 carries the volume. Near-Opus quality on coding and agentic work, with the full effort ladder (low → max) — and the chair dials that ladder per task.
- Opus 5.5 takes the hard slices directly. Architecture tradeoffs, irreversible migrations, complex multi-system implementation and all security review are assigned straight to Opus, with no failed Sonnet pass required.
- Escalation is one-way. Sonnet returns…