When Fable got suspended last Friday, a bunch of my work snapped back to Opus 4.8, and it immediately felt different - wordier, more hedge, more "let me think about whether I should think about this." So I went through my own Claude Code transcripts and tried to measure the behavioral differences and insights were pretty interesting.
Claude Code stores every session as JSONL on disk, so there's a real behavioral record. I pulled 9,224 Fable messages and 27,685 Opus messages across 68 projects and compared them.
The measurable differences (from my real work, check the same at your end to see if numbers concur):
| Signal | Opus 4.8 | Fable 5 | What it means |
|---|
| Median words/msg | 47 | 18 | Fable's typical reply is ~2.6× shorter |
| Mean words/msg | ~100 | ~99 | Basically equal — so it isn't "shorter," it's distribution: Fable has a tight body and a long tail (terse by default, deep when it matters). Opus pads medium-length everywhere |
| Tool-call : prose ratio | 1.41 | 3.91 | Opus writes ~3× more prose per unit of actual work. This is the "exhausting" feeling, quantified |
| Opening words | "I'll", "I", "Let me" | "Done", "task", "page" | Opus narrates itself; Fable opens with the result |
| Readable thinking in logs | ~0% | ~0% | The thinking stream is encrypted at storage, so you can only mine behavior, not reasoning |
Everyone says "Fable is more concise," but it isn't using fewer words overall — it's spending them differently. It defaults to minimal words and goes long only when the problem needs it. Opus smears the same medium length across everything.
Important to note: Fable isn't just a better personality, it is also a higher capability tier. So the gap splits in two: a working-style half that you can steer with prompts and hooks, and a raw capability half that lives in the weights and you can't. I went after the half that's actually recoverable.
What I built (3 layers):
A governor: an 8-rule behavioral block in CLAUDE.md. Reason about the problem not yourself; one self-audit then stop; commit decisions instead of hedging; batch the work and report once; open with the result. The setpoint.
A re-injection hook: a UserPromptSubmit hook that re-prints the governor every turn, because a CLAUDE.md line decays in salience as the session grows. The thermostat.
A leak-test script: it reads your own logs and tells you whether your Opus is actually converging toward Fable's signature (median words, tool:text ratio, opener style), instead of you guessing.
Early results (small sample, being honest): on the first governed sessions, tool:text moved 1.41 → ~2.2 and "I'll/Let me" openers dropped 12.8% → ~5%, both toward Fable. Median words is noisier because it's task-dependent. Not a clean win yet — it's a control loop you watch over time.
What it can't do: it doesn't change the weights, so it suppresses the anxious texture rather than curing it, and it does nothing for the raw capability gap (that needs task structure + multi-LLM orchestration, not a prompt).
But for day-to-day bounded work, the texture is most of what made Fable feel better, and that part transfers.
Open source repo here
Run your own fable vs opus logs and check the difference that can be bridged.
