Persistent task tracking and coordination for coding agents that outgrow a single chat session.
Why read Steve Yegge?
Read Steve when your coding agent forgets unfinished work or a growing plan becomes hard to execute. His Beads writing explains how to turn plans into tasks with dependencies and retain that working record when you restart an agent.
Gas Town extends that problem to several agents: who picks up work, how changes reach the merge queue and how a replacement session finds its task. The launch essay is a detailed introduction for readers already running coding agents, with concrete descriptions of the system's early failure modes. His current site also documents Gas City.
Start with the original
Selected work
Workflow ·
Beads Best Practices
How can a coding agent resume useful work after a restart? Start with planning outside Beads, recording dependencies and giving each session one task.
Project walkthrough ·
Welcome to Gas Town
What needs coordinating when several agents work on a repository? His launch walkthrough describes task ownership, persistent handoffs, worker supervision and a queue for merging changes.