Can an AI-generated world engine run entirely in the browser?
LAAS — Procedural WebGPU World
LAAS is a fully procedural 4x4 km old-growth world — terrain, forests, atmosphere, water and particles — generated at boot in desktop Chrome using WebGPU, with every mesh, texture and light created by code at runtime rather than downloaded. It is a study in what a single frontier-model-written engine can do unmodified.
- WebGPU
- Claude Fable 5
- Procedural generation
Relevant services: AI Digital Teammates · Thrivbe AI
Hypothesis
Frontier models can now write an entire 3D world engine — not assets, the engine. Can a fully procedural world, generated at boot with no downloaded meshes or textures, actually run in a stock desktop browser?
What we built
A desktop Chrome/WebGPU experiment: a fully procedural 4×4 km old-growth world generated at boot — terrain, forests, atmosphere, water, particles — with walk and fly exploration. Every mesh, texture, and light is created by code at runtime. The codebase originates from the Fable 5 community's world-demo lineage; our deployment is a study in what a single frontier-model-written engine can do unmodified.
Learnings
- WebGPU is ready for this class of work — the bottleneck is no longer the browser, it's generation time at boot.
- AI-written engines have a recognisable style: aggressive proceduralism (nothing is an asset, everything is a function) because that's the cheapest thing for a model to express.
- Running someone else's AI-generated code untouched is itself an experiment: it tells you how portable and self-contained this generation of model output really is.
Log
- 2026-07-10 — Listed on the Thrivbe experiments hub.
- 2026-07-09 — Deployed the world demo to Vercel; verified 4×4 km world boots and runs on desktop Chrome.