Opus 4.8 vs Fable 5, One Prompt Each: We Made Them Build a Game and an Interchange — and They Split 1–1

Benchmarks tell you what a model scores. They don't tell you what it's like to hand two frontier models the exact same creative brief and watch what comes back. So we ran our own head-to-head: Anthropic's Claude Opus 4.8 against Claude Fable 5, two tasks, identical prompts pasted into fresh chats, one shot each — no retries, no follow-ups, no cleanup. Everything you see below is exactly what each model produced (we only resized the outputs to fit the page).

Test 1: An animated highway interchange, in pure SVG

The brief: a top-down view of a busy highway interchange as a single self-contained SVG — two roads crossing on different levels, connecting ramps, at least 12 vehicles following the curves of the roads in both directions, correct layering so cars vanish under the overpass, and a seamless loop. No scripts, no text, no external assets. Both models delivered in roughly five minutes. The results run live below.

Opus 4.8 went for a full cloverleaf: lush terrain, gradient asphalt, drop shadows under the bridge, and graceful circular ramps. It's the more atmospheric scene — until you follow a car onto a ramp. The loops are beautiful, but they don't actually connect to anything: traffic circles around them and returns to nowhere, like an interchange designed by someone who has only ever seen one from a plane.

Fable 5 solved the harder geometry problem: its ramps genuinely peel off one road and merge into the highway, which is the thing that makes an interchange an interchange. But it fumbled the traffic rules — watch a car come down a ramp and join the freeway, and you'll see it merge straight into oncoming traffic, cheerfully driving against the flow it just joined.

Round 1 goes to Fable 5. Wrong-way drivers are a bug; ramps that connect to nothing are a missing feature. Fable built the thing we asked for and got a detail wrong — Opus built a gorgeous picture of a different thing.

Test 2: A playable Space Invaders, one HTML file

The brief: a complete Space Invaders — marching invaders that speed up as they thin out, return fire, three lives, destructible bunkers, waves, score, start screen, game over and win states, restart — all in a single self-contained HTML file, all graphics drawn in code. This one separated the two models on a different axis: time. Opus 4.8 finished in 26 minutes; Fable 5 took 40.

Both games below are fully playable. Click inside a game first to give it keyboard focus — arrows or A/D to move, Space to fire. You'll want a keyboard, so this is one for desktop readers.

Opus 4.8's build — 26 minutes

Opus produced the better-looking game and it isn't close: a glowing CRT cabinet frame, scanlines, phosphor-green typography, color-tiered invaders with a proper two-frame walk cycle, and a start screen that looks pulled from a 1979 arcade. The polish has one crack in it — the help button simply doesn't respond — but the moment-to-moment feel is the strongest thing either model produced all day.

Fable 5's build — 40 minutes

Fable's version is plainer to look at — closer to a faithful arcade reproduction than a styled cabinet — and it spent 14 more minutes getting there. What it bought with that time is correctness: every single feature in the brief works. Bunkers erode pixel by pixel, waves drop lower and faster, the pause works, the restart works, the high score survives a reload. We went looking for the broken button and couldn't find one.

Round 2 goes to Opus 4.8. When everything important works in both builds, the game you'd actually show a friend wins — and that's the one with the CRT glow, even carrying a dead help button.

The verdict: 1–1, and a pattern

A split decision, but not a random one. Across both tasks, Fable 5 optimized for the spec — connect the ramps, make every button work — and paid for it in time and in style points. Opus 4.8 optimized for the experience — the scene that looks right, the game that feels right — and let a functional detail slip through in each round. Two frontier models, same prompts, same company: one engineer, one art director. With one run per task this is an anecdote, not a benchmark — but it's a vivid one.

And this scoreboard isn't final. This head-to-head is just the opening round of an ongoing BitsMinds series — we'll keep handing both models new one-shot builds, raising the difficulty each time, until something decisively breaks the tie. The next tests are already on the bench.

Now it is your call: which result do you prefer? Opus 4.8’s cinematic CRT cabinet with its one dead button, or Fable 5’s plainer build where everything simply works? Scroll back up, watch both interchanges, play both games — then pick a side and share this article with your verdict. Until the next round, the real tiebreaker is you.