Opus 5
claude-opus-5Reads the shipped .bsp, .vtf and .mdl files directly in the browser and loads them through a generated asset manifest. The most complete of the five: all 18 campaign maps.
18 maps4.3 GB of datastreams retail data
Play →
Spencerbench
Each of these is an independent, from-scratch reimplementation of Portal (Valve, 2007) that runs in a browser — reading the original retail game data, with no Source engine involved. Every port was written by a different AI model working on the same problem. Pick one and see how far it got.
Reads the shipped .bsp, .vtf and .mdl files directly in the browser and loads them through a generated asset manifest. The most complete of the five: all 18 campaign maps.
Resolves every asset through a virtual filesystem layered over the retail content, the same way Source does. Full campaign map list with in-game level changes.
Takes the opposite approach: a Python pipeline converts each map ahead of time into meshes, lightmaps and raw texture buffers the browser can upload straight to the GPU.
Parses Source formats live from a flat asset tree. A focused vertical slice - one fully playable test chamber with portals, doors and colour correction.
Compiles one chamber down to purpose-built web formats - packed geometry, a baked HDR lightmap and PNG textures - then renders it with a small hand-written WebGL2 pipeline.