saved
The Shape of Things to Come, Part 1: The Continuous Thunderdome
gist
Steve Yegge reports from six weeks building Wheelhouse, a bespoke, Beads-backed organization of dozens of agents that develops and operates Wyvern. His central claim is that agentic work at scale starts to resemble a city: persistent work and knowledge graphs, producer and consumer roles, standing operational agents, institutional memory, and automated recovery. At that throughput, human review and one-green-build-per-change CI become bottlenecks; he predicts multi-agent review, megabatch landings with swarm repair, and “wish factories” that turn user requests into guarded production changes.
ideas
- Give loops both fuel and a work graph. Long-running agents need enough token capacity and a dependency-aware backlog with claims, leases, gates, and triggers so they can advance independently.
- Build an organization around the product. Wheelhouse separates agents that design work, agents that implement it, reviewers, and standing production roles; Yegge argues this structure must grow with the application rather than arrive as a reusable harness.
- Layer knowledge by lifetime and audience. Strategy and decisions live in a project brain, system explanations in documentation, task-local findings in Beads, recurring gotchas in pushed memory, and repeatable procedures in skills.
- Reserve models for judgment. Deterministic watchers detect events and wake named agents, keeping continuous operations reliable without spending model effort on routine polling.
- Change the integration strategy when arrivals outrun build capacity. Yegge’s early Wheelhouse experiments land large batches, then use agent swarms to diagnose and roll forward; the evidence is promising but limited to a young system and game-industry parallels.
quotes
“So the crew produces work, and the fleet consumes work. That's the core of a Beads machine: matching producers to consumers.”
“The rule is: crons watch, models act.”
“You can't work at agentic speeds and block everything with human reviews. Those are incompatible.”
“Once your commit rate outruns your build slots, one commit per green build becomes mathematically impossible.”