Steve Yegge says the skill of the year is running a fleet, not prompting an agent

Steve Yegge reframed agentic coding this week and I think he's right, which is annoying because it means the thing I just got good at is already the wrong unit of work.

In his latest piece, Yegge lays out a six-wave chart of coding agents and plants a flag: 2026 is the year of "agent fleets." His current work is the proof. Gas Town is a multi-agent orchestrator built to run 20 to 30 parallel agents. Beads is a memory and issue-tracking system built specifically for AI agents rather than for humans. The argument underneath both: the skill that matters now is coordinating a swarm, not steering one session.

What makes this credible instead of vaporware is that the same pattern is showing up everywhere at once. There's a whole cluster of new fleet-control tools appearing on GitHub. Superset bills itself as running "an army of Claude Code, Codex." Agent-of-empires ships a TUI, web, and mobile control surface. LobeHub calls its role "Chief Agent Operator." When three teams independently build a dashboard for supervising dozens of parallel agents, the market is telling you the unit of work changed.

But here's the part builders need to hear before they go spin up 30 agents. The economics are not free. Production data from 2026 puts the multi-agent token tax at roughly 58% overhead for independent setups and around 285% for centralized ones versus a single agent. And a separate retrospective on what actually survived to production found that every system that worked shared one of three anchors: explicit phase gates, shared artifacts both agents read and write, or a final supervisor that reconciles the output. Free-for-all swarm chatter degraded every time.

So the Beads insight is the sharp one. Yegge didn't just build an orchestrator, he built an issue tracker for the agents to coordinate through. That's the shared artifact. That's the phase gate. If you're already running a harness with a ticket backend, you're closer to a fleet architecture than you think. The move isn't "add more agents." It's "give your agents a durable place to hand off work." I'd start there before I touched the parallelism dial, because 30 agents with no coordination anchor is just 30 ways to burn tokens and merge conflicting summaries.