three-quake
Ricardo Cabello wrote Three.js. He spent five months rebuilding the 1996 Quake engine in JavaScript by hand, with Claude co-authoring nearly every commit.
Quake has run in browsers for a decade: QuakeJS and friends took id Software's original C and machine-compiled it to run on the web, id's code untouched underneath. three-quake is a different animal. Ricardo Cabello — mrdoob, the author of the Three.js graphics library that half the web's 3D runs on — re-authored the engine itself in JavaScript, from scratch, over roughly 265 commits between late January and late June. It's playable now at mrdoob.github.io/three-quake, shareware episode bundled.
265 commits, five months — an expert-driven port, not a one-shot demo
What makes it worth a look is the commit archaeology. The one-paragraph README lists no features; the depth is in the log, where Claude is co-authored on nearly every entry and the entries read like a working engine programmer's week: 'Fix SV_AirAccelerate bug', 'Add brush entity collision', 'Fix audio spatialization to match original Quake', 'Implement save/load'. These are the load-bearing internals of a 3D game — the movement physics, the world-collision math, the positional sound — rebuilt in a new language rather than transpiled through a black box.
The pedigree is the point. A browser Quake is not news; a from-scratch engine port, hand-driven by the person who wrote one of the web's foundational graphics libraries, with an AI agent as sustained co-author across five months, is a concrete data point on what agent-assisted software work looks like when an expert stays in the loop the whole way — not a one-shot demo abandoned at the first playable frame, but a long, real project that shipped.
Open mrdoob.github.io/three-quake to play it in a tab, then read the commit log on GitHub — that's where the engine work actually lives.
Open the demo at github.com →The lenses
The facts
Concepts
How this connects
Tap a node to open it