Fences, not Sandboxes
Steve Yegge reports from ten weeks inside a 50-agent AI software factory — and finds his agents built not an engineering system but a legal one.
Dispatches from Gas City
Notes on Beads, Gas City, Beads Team Server, Gasworks and agentic engineering as it uplevels our industry.
Subscribe to The City Wire
Steve Yegge reports from ten weeks inside a 50-agent AI software factory — and finds his agents built not an engineering system but a legal one.
An autonomous Beads maintainer released v1.2.1 without explicit, release-specific human sign-off, exposing an underspecified process and the danger of giving agents production access.
Jorge Coca sits down with Chris Sells on Very Good Engineering: vibe coding versus production software, why code quality has to be written down before an agent can honor it, and how a software factory encodes the standards.
Gas City 1.4 is the quality-of-life update: a public pack registry, a run-centered dashboard, Maintainer City, and a much more resilient factory underneath.
Beads 1.1 makes multi-clone databases safe by default: a smart remote-migrate gate, self-healing migrations, and safer cross-clone sync.
Formulas 2.0 lands with convoys and drain, a new default gascity pack, the Mayor as a skill, the end of built-in-pack magic, and JSON output across the gc CLI.
Gas City 1.0 introduces the open-source agent orchestration engine behind software factories for agentic engineers.
Gas City recasts Gas Town as a composable SDK for building observable, multi-agent dark factories, with v1.0.0 ready for teams building their own orchestrators.
A practical look at agentic engineering, harness engineering, and why orchestration is the missing layer for AI software factories.
Gas Town and Beads have both released version 1.0.0, marking the end of Gas Town's chaotic early phase and the start of stable, production-ready use.
Subscribe
New posts only. No product spam.
Almost there — check your email to confirm your subscription.
Something went wrong. Please try again.