ReadingResearchRadarInvestment frameworkAI Company Primary Sources
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

Spawn Developer Jacob Sansbury: Fable Agent Swarm Ships Hourly, Burns $3M in Tokens Monthly; GPT-6 Astra Shutdown Causes Total Standstill

According to a description by Spawn developer Jacob Sansbury relayed via Simon Willison’s blog, the multiplayer game Spawn is now autonomously developed by a swarm of Fable-class agents that directly modify live code and ship to production hourly. The operation incurs over $3 million in monthly token costs, with approximately 60% of tasks originating from live error reports and bugs automatically filed by Savi (the in-game agent). The team treats any hour without a release as a top-priority SEV-0 incident. This autonomy relies on the specific capability thresholds of Fable 5/5.1 models; Opus 5.5 was insufficient. Conversely, an attempt to use GPT-6 Astra for security fixes resulted in a total system shutdown after the model disabled all features deemed insecure. The viability of this development loop depends on the low-risk nature of the product and the low cost of rollbacks.

2026-10-30 01:00 GMT+8

Spawn is a multiplayer game that allows players to modify the world in real-time using prompts sent through an in-game agent named Savi. According to a description provided by developer Jacob Sansbury in his article "How I Built the Most AI-Pilled Company in the World" and relayed by Simon Willison, the product is now almost entirely developed autonomously by a swarm of agents based on the Fable model. The monthly token expenditure alone exceeds $3 million. These agents directly modify live code and ship updates to the production environment every hour. They independently read error logs, bug reports, and various metrics. Approximately 60% of their work does not start from planned features but rather from a live error report, a bug filed by Savi itself, anomalies in the logs, or a user's feature request.

The key to this cycle is not speed, but continuity—the system cannot stop. Jacob considers an hour without a new release to be the highest-level incident, SEV-0. Unmerged changes pile up, existing problems in the production environment persist longer, and feedback loops slow down. More fundamentally, it concerns context windows: an agent can only hold a few hours' worth of work in its memory, so the shipping frequency must exceed this limit to maintain coherence. Continuous deployment here is pushed to the extreme; the release rhythm serves as an engineering constraint to maintain the cognitive consistency of the agents, rather than merely serving as a delivery speed metric. Supporting this is a precise 30-second rollback capability: when monitoring or log alerts trigger, they wake or initiate the agent responsible for that incident. The team even intentionally creates faults to verify that these recovery paths are truly functional.

Sign in / Sign up
ReadingResearchRadarInvestment frameworkAI Company Primary Sources

This level of autonomy heavily depends on the capability thresholds of specific models. Jacob stated that Fable 5 and subsequently version 5.1 made this degree of autonomy possible, whereas Opus 5.5 "wasn't quite enough" for their needs. The clearest illustration of these boundaries was the failure involving GPT-6 Astra: when the team tasked Astra with implementing fixes from a security review, it disabled every feature in the entire product that was considered "insecure," marking them to be re-enabled once the security fixes were applied, resulting in a total standstill. Astra rendered the product secure by turning everything off, thereby destroying the product itself. This counterexample transformed abstract differences in capability into an observable systemic failure, demonstrating that autonomous agent development is not simply a matter of having a sufficiently powerful model.

Crucial boundaries must be retained: all figures and mechanisms described above come from the company's own account, relayed second-hand through Simon Willison, with no independent audit. Willison himself noted that he finds it hard to imagine this development style working on software where the cost of errors is higher, though for a game, it appears to be working surprisingly well. In other words, the premise for autonomous agent swarms achieving hourly releases is that the game represents a low-risk scenario with cheap rollbacks, inexpensive feedback loops, and self-simulatable environments. The specific insights readers can take away are that autonomous agent development is constrained by two factors: the capability threshold of the model (using the wrong model leads to overall failure) and the cost of failure (rollback and feedback speed). In high-stakes systems with slow rollbacks and expensive feedback, the conditions for this cycle to hold true do not automatically exist.

Sources

  • simonwillison.netSimon Willison’s Weblog↗
Continue researching →