I asked Claude Opus to recreate The Matrix opening scene in Lego
Checking the source page briefly so the paragraphs stay factual and don't invent details.A demo at marksmayo.github.io/lego-matrix stages the opening of The…
By Dillip Chowdary • Aug 04, 2026 • Source: HN Claude/Codex/Fable
Checking the source page briefly so the paragraphs stay factual and don't invent details.A demo at marksmayo.github.io/lego-matrix stages the opening of The Matrix as a Lego scene after Claude Opus was asked to rebuild that sequence. The project is public on GitHub under marksmayo/lego-matrix and was submitted to Hacker News, where it had 4 points and 4 comments at the time of the thread.
The page runs the Wachowskis screenplay scenes 1 through 11 in the browser with three.js and rigid-body physics. Minifigures act out the beat; bricks are treated as load-bearing geometry. Runtime is about four minutes. Controls are mouse for camera, space to pause, and arrow keys to skip. The implementation is plain JavaScript files served as a self-contained web demo rather than a native app or video export.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
For engineers, the interesting part is not the meme framing but the stack choice: a full cinematic beat as interactive 3D with real-time physics, not a rendered clip. That forces the model-assisted code to hold scene graph layout, timing, collision, and camera work in one browser session. Commenters noted jitter in places and better behavior in Chrome than Firefox, which is the usual browser-side WebGL and JS performance gap when no hand optimization has been applied.
The piece sits next to similar Claude Opus demos that rebuild film or book openings in three.js, including the Karpathy-style Lord of the Rings paragraph recreation discussed on the same thread. Competitive pressure here is less product vs product and more model vs model on long, multi-file creative coding tasks: can the assistant keep a coherent multi-scene 3D production without the human rewriting the whole architecture.
If you build with agentic coding tools, treat this as a stress test pattern: ask for a timed, multi-scene three.js scene with physics and ship the output as static JS on GitHub Pages. Watch browser differences early, measure frame time on Firefox and Chrome, and keep the source small enough to run offline so reviewers can separate model quality from network lag.
Advertisement