**Building a multiplayer game world with autonomous Fable-class models** > <p\>
原帖
**Building a multiplayer game world with autonomous Fable-class models**
> <p\><strong\><a href="https://twitter.com/jsnnsa/status/2115623382721126826"\>How I Built the Most AI-Pilled Company in the World</a\></strong\></p\>
> Don't be put off by the clickbait headline, this piece by Jacob Sansbury describing how they are building <a href="https://spawn.co"\>Spawn</a\> is a fascinating exploration of the bleeding edge of what's possible with agentic engineering against frontier models.</p\>
> <p\>Spawn is a massively multiplayer gaming environment where players can use prompts (to the in-game agent, Savi) to modify the game world.</p\>
> <p\>I fired it up on my phone for a few minutes and was able to prompt a castle into existence, then a dragon, then ride the dragon to fly around that castle.</p\>
> <p\><img alt="Two mobile screenshots side by side from a 3D voxel-style game. Left: a first-person view from the saddle of a small teal dragon, its neck with pale diamond markings and two curved white horns in the foreground, flying toward a dark stone castle with tall teal-gray conical spires, glowing windows and teal pennants, on a rocky island in a lake with green and snowy hills behind. Top bar: profile icon, "keep it", "your den" dropdown, "+ new game" button and a "..." menu. Right side: icon buttons and a portrait of a white-haired, freckled character labeled "tap to talk". Bottom right buttons: "JUMP" and "USE". Right: the same game with the chat panel open over the castle scene. Top bar: "your den" dropdown, "+ new game". Button: "earlier ↑". User message: "Make the dragon smaller and land it next to me again". Replies from the white-haired character: "on it. shrinking it to a pony-sized dragon and landing it right beside you." Then: "it's a little dragon now and you're already up on it over the lake. your view sits right in its saddle, horns ahead. fly back to the house and look down. saw your screen just now: flying over the water, the neck and horns ahead, the house on the far shore" Then: "oh, idea: USE while flying could breathe fire instead, with JUMP held to land. want it?" Input box: "what do you want to bring in?" Buttons below: upload, a small pixel-art icon, "lock in" and a microphone." src="https://static.simonwillison.net/static/2026-10-29/IMG\_9406.webp" /\></p\>
> <p\>By Jacob's telling, Spawn is now being developed autonomously by a swarm of Fable-powered agents costing over $3 million in tokens <em\>per month</em\>:</p\>
> <blockquote\>
> <p\>Our agents change the live code directly and ship to production hourly, so they read every error, bug report and metric themselves. About 60% of our work starts from a production error, a Savi bug report (Savi is the AI you build games with in Spawn), something odd in our logs, or a feature request.</p\>
> <p\>Savi files bugs herself. When a user hits one, or Savi hits one in the product, she files it. It goes straight to an agent that decides whether it's a real bug to fix, something we won't fix, or intentional design that needs a decision. Usually it becomes a change, delivered to that user within an hour, with a message in the same chat.</p\>
> </blockquote\>
> <p\>This is <a href="https://en.wikipedia.org/wiki/Continuous\_deployment"\>continuous deployment</a\> turned up to 11:</p\>
> <blockquote\>
> <p\>A loop this tight only works if it never stops, so we treat an hour without a ship as a SEV-0, our most severe kind of incident. Unshipped changes pile up, and every problem already in production lasts longer. The feedback slows down too. An agent can only keep a few hours of work in its head, so shipping faster than that actually helps it stay coherent. \[...\]</p\>
> <p\>We can roll back a broken change in 30 seconds, exactly where it's broken and nowhere else....
**来源信息**
- **来源**:Simon Willison 博客
- **分类**:ai-products
- **发布时间**:2026-10-30 01:00(北京时间)
- **原文**:[打开原文](https://simonwillison.net/2026/Oct/29/how-i-built-the-most-ai-pilled-company-in-the-world)