Opus 5 Built a Rocket League Clone — Then Played It

Hours after Claude Opus 5 launched, developer am.will (@LLMJunky) dropped a five-minute clip that X immediately filed under “psychosis”: Opus 5 had built the best Rocket League–style clone he’d seen — car reflections, arena detail, playable bots — while burning only ~27% of a Claude Max 5x sub.

Then the follow-up: Opus didn’t just ship code. It played the game to verify mechanics.

This explainx.ai post is the builder decode — stack, links, what “Opus controlling the game” actually means, and how it fits Anthropic’s day-one coding pitch.

August 2 update: Karpathy’s Opus 5 Lord of the Rings world makes the verification contrast clearer: this Rocket Arena build closed the loop by letting the agent play, while Karpathy’s model had to audit a moving world through slow screenshots.

Demo pulled from am.will’s announcement thread — sound on if you want the full effect.

TL;DR — What People Are Asking

Why This Demo Hit Harder Than a Bench Chart

Anthropic’s launch sold Opus 5 as near-Fable intelligence at half the price with Frontier-Bench SOTA. am.will’s thread is the complementary vibe: I expected a cheaper Fable and got a model that owns games and 3D polish.

Concrete claims from the thread:

1. One-shot-ish build quality — car, reflections, arena details called out as best-in-class for AI-built RL clones
2. Credit efficiency — ~27% of Max 5x for the session (not “free,” but not a full weekly wipe)
3. Agentic loop closed — build → test → play to confirm feel
4. Open artifacts — Vercel playable + GitHub am-will/rl-opus
5. Boris Cherny reaction — Claude Code lead replied “Neat!!” on the thread

That last point matters for builders: this is the kind of long-horizon UI/game work ClaudeDevs said Opus 5 was built for (developer migrate guide).

Opus Playing the Game

From the follow-up: “This is Opus controlling the game entirely.”

Read this carefully:

• Not “Opus 5 has a built-in Rocket League brain in the weights”
• Yes “an agent session (Claude Code / computer use / browser tools) can operate the running web game as a verifier”

That distinction is the interesting part for agent harnesses. Verification used to mean unit tests and screenshots. Here verification means closing the gameplay loop — the same direction as Anthropic’s early-access quotes about models opening pages at mobile widths and fixing fold bugs before handoff.

If you’re building product agents, the pattern is: ship artifact → instrument play/use → feed failures back. Games make that visceral; CRUD apps can do the same with scripted browsers.

What’s Actually in the Repo

From the public Rocket Arena README:

npm install
npm run dev

Notable gameplay fidelity called out in-repo: Rocket League kickoff spawns, demolitions only when supersonic, boost pads left alone at 100%, goal pyro + slow-mo, wheel ember trails for supersonic, bot roles (closest ball vs support).

Online note: Vercel serves static/game; a Cloudflare Worker holds WebSockets (server/ in the repo) — already deployed on the free tier for ~130 matches/day per the README.

Starting Prompt Shape (Not Magic)

am.will linked an earlier seed prompt along the lines of: Build a polished browser-based 3D Rocket League–style game using Three.js… first screen is the actual game… use real physics… Then iterated: practice mode, infinite boost, steering tweaks, audio, orb boost pads, rounded goals/ceilings.

That matches Anthropic’s Claude 5 context engineering advice more than prompt theatre: clear product intent + iterative refinement + rich running artifact, not a 4,000-word system prompt.

Also pairs with thin prompts / thick artifacts — the game is the thick artifact.

vs Prior Fable and Sol Runs (Same Author)

This is one developer’s longitudinal taste test, not a blind arena. Still useful: same person, same genre, multiple frontier models — Opus 5 wins on polish for this task class.

How to Reproduce the Workflow (Not the Exact Session)

1. Start Claude Code on claude-opus-5 (migrate guide)
2. Keep effort high (Opus 5 default) for multi-file 3D work
3. Seed a playable-first prompt (Three.js + real physics + no landing page)
4. Ask for acceptance checks: play for 30s, fix camera/steer feel, add audio
5. Prefer a running Vite app as the reference over screenshots alone
6. Optional: computer-use / browser loop so the agent can drive after each change
7. Rightsized CLAUDE.md — gotchas only; don’t hobble with “never use X library” bans (context engineering)

Build a polished browser Rocket League–style arena using Three.js + Rapier.
First screen = the game. Keyboard + gamepad. 1v1 bot. Real boost/jump/flip feel.
After each feature, open the app and play 20 seconds to verify steering and camera.

Multiplayer Follow-Up

Later the same day, am.will posted that multiplayer was working — plug in Xbox / PS5 / Steam controllers, join with a room code. That lines up with the README’s Cloudflare Worker rooms: one browser hosts the match authority; the joiner’s car is predicted locally and corrected toward the host.

For agentic coding, that is a second verification surface: not only “does 1v1 against a bot feel right?” but “does networked input still feel fair?” Opus 5’s long-horizon story is exactly the kind of stack that can keep those threads alive without you re-pasting the architecture every turn.

What This Means for Builders Tomorrow

1. Games are a stress test for agency — continuous visual feedback, physics edge cases, “feel” bugs that unit tests miss.
2. Credit efficiency matters — if Opus 5 can land a 3D playable at a fraction of a Max 5x week, the “Fable for everything” default weakens for this workload class.
3. Verification is becoming embodied — agents that can use what they built will beat agents that only ls and npm test.
4. Open demos compound — Vercel + GitHub let other people fork the acceptance criteria, not just applaud a video.

If your team evaluates models on “write a React form,” you will miss this delta. Add one visual + interactive task to your private harness: Three.js toy, canvas tool, or small game loop with a play-script.

Copy-Paste Eval Prompt

Using Three.js + Rapier in a Vite app, build a minimal playable car-arena:
drive, jump, boost, one ball, one goal. First screen is the game.
After implementing, open the app and play for 30 seconds.
Fix the first three feel bugs you notice (camera, steering, collision).
Commit after each fix with a one-line note of what felt wrong.

Run that on Opus 5, Fable, and Sol. Score on playability, not LOC.

Honest Limitations

• Vendor-adjacent hype: one viral demo ≠ production SLA.
• Credit math is personal: 27% of his 5x Max session — your burn rate depends on effort, Fast mode, and tool loops.
• “Opus played” depends on tool access (browser / computer use), not a special game API.
• IP / platform: Rocket League is Psyonix/Epic IP — this is a fan-style clone for demo/learning; don’t ship a commercial clone on someone else’s IP.
• Repo was fresh and lightly starred at coverage time — expect rapid churn.

Related on explainx.ai

• Opus 5 remade Pokémon in 3D — and the starter scene is unsettling
• Top 10 Claude Opus 5 use cases
• Did Opus 5 one-shot Call of Duty? Claude of Duty
• Top 10 Claude Opus 5 game prompts — full text, 10 builders
• Claude Opus 5 launch — benches, charts, Fast mode
• Opus 5 for developers — migrate, effort, API
• Claude 5 context engineering — /doctor
• Claude Code model vs effort
• Thin prompts, thick artifacts, thin skills
• Generate images in Claude Code
• TryAI Canvas Arena — drawing frontier models
• Command & Conquer Generals Fable port

Sources: X — Opus 5 Rocket Arena announcement · X — Opus playing · Play · GitHub am-will/rl-opus · Anthropic Opus 5

Demo claims and credit usage as reported by the developer on July 24–25, 2026. Re-verify the live Vercel URL, repo, and your own Max limits before treating this as a reproducible recipe.

Update — July 26, 2026: Same Opus 5 demo week — Matt Shumer’s Claude of Duty (procedural Three.js FPS, zero art files).