Fable 5 vs Opus 4.8, One Prompt Each: Four Builds, Dead Level at 2–2

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, four 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.

Test 3: An animated aquarium, in pure SVG

The brief: a self-contained animated aquarium as a single SVG — a tank of fish swimming among plants, rocks and rising bubbles, everything drawn and animated in markup, with no scripts and no external assets. It is a gentler prompt than the first two, which is exactly what makes it revealing: with nothing technically treacherous to trip over, each model's instinct shows in the open. Opus 4.8 finished in 9 minutes; Fable 5 took 10.7. Both run live below.

This time the tell is behavior, not geometry. Opus 4.8 drew the more charming fish — rounder bodies, glossy eyes, little smiles — and set them cruising along graceful curves. But every one of those curves runs from beyond the left edge to beyond the right, so the fish swim clean through the walls and wrap around, as though the tank held an open ocean. Fable 5's fish are plainer, yet each one patrols a closed loop and flips to face the new direction the moment it turns — they behave like fish in a box of water. Fable also took the word aquarium more literally, framing an actual glass tank on a stand, complete with a chest, a starfish and a darting school; Opus painted a lovely open-water scene and let its cast drift off the edges.

Round 3 goes to Fable 5. Opus's fish are genuinely cuter — a real mark in its favor, and the reason this round is closer than the ramps were. But the one thing that makes an aquarium an aquarium is the glass, and only one model's fish ever behaved as if it were there. A charming fish that swims through walls still breaks the spell; a plain one that turns back keeps it.

Test 4: A cinematic rocket launch, in one HTML file

The brief: a self-contained web page that animates a rocket launching — countdown, ignition, liftoff and ascent — with a mission-control HUD. Both models reached for the same tool without being told to: a real-time 3D scene built on Three.js and WebGL, pulled from a CDN. And both made the same first decision — the setting — in opposite directions. Opus 4.8 finished in 27.9 minutes; Fable 5 took 35.5. Both launches run live below (give them a moment to load the 3D engine).

Opus 4.8's build — 27.9 minutes, launched by day

Opus set its launch in daylight — a blue sky fading to a warm horizon — and drew a cleaner, simpler rocket. It also kept a firm hand on the exhaust: modest bloom, a tempered engine glow, smoke deliberately held below the glow threshold. The payoff is legibility. The rocket reads clearly the whole way up, from countdown to engine cutoff; you can always see the thing that's launching. During the build, Opus even flagged its own first-pass exhaust as too intense and dialed it back on its own — the same self-checking instinct that decided the earlier rounds. The one blemish is on the vehicle itself: the tail fins don't sit flush against the hull, splaying slightly away from the body where they should meet it.

Fable 5's build — 35.5 minutes, launched at night

Fable went for spectacle: a night launch under a moon and distant city lights, a beautifully detailed rocket with panel seams and a painted-on name, volumetric spotlights raking the pad. On a still frame it is the more impressive build by a distance. But in motion the drama eats its subject. The bloom is cranked, the engine lights are enormous, and against a black sky the exhaust blooms into a wash of white that swallows the rocket for most of the ascent — you spend the launch staring at a brilliant glare where the vehicle should be. It is exactly the kind of thing a single playthrough would have caught, and Fable never checked.

Round 4 goes to Opus 4.8. Fable built the more beautiful scene and the more beautiful rocket, then let its own lighting hide the one object the whole animation exists to show. Opus built the plainer launch, noticed its exhaust was drowning the frame, and fixed it before shipping. A launch you can watch beats a launch you can only squint at.

The verdict: 2–2, and a pattern that just got complicated

Two rounds each — and a tie more telling than a clean win would have been. For three rounds the split looked stable: Fable 5 chased the spec (connect the ramps, make every button work, keep the fish in the tank) while Opus 4.8 chased the experience and let one functional detail slip each time. The launch round flipped the script. This time it was Fable that reached for pure spectacle — a gorgeous night launch — and shipped it without noticing its own glare had swallowed the rocket, while Opus played the disciplined one, catching its over-bright exhaust mid-build and toning it down. So the real thread is not "one model is the engineer, the other the artist" — it is that each round goes to whichever model actually checks its own work, and neither does that every time. Two frontier models, same prompts, same company, four one-shot builds: this is still an anecdote, not a benchmark — but it's an increasingly consistent 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, to see how durable the pattern really is. 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, aquariums and rocket launches, play both games — then pick a side and share this article with your verdict. Until the next round, the real tiebreaker is you.