The Gas City Guide

Understand Gas City without the noise

Evergreen notes on software factories, multi-agent orchestration, durable agent work, and how Gas City and Beads fit beside the tools teams already use.

01 / Gas City

Guide

Build an AI Software Factory

Learn what an AI software factory is, how Gas City runs one on Beads, and how to start with a repeatable coding workflow on your own repo.

Guide

Open-Source Agent Orchestration

See what an open-source agent orchestration platform should leave under your control, from workflow configuration and coding-agent choices to durable Beads work.

Guide

Coordinate Multiple AI Coding Agents

Coordinate coding agents with explicit Beads work, blocking dependencies, isolated worktrees, repeatable Gas City workflows, and a human review gate.

Guide

An AI Software Factory in Practice

Watch Maintainer City operate across a 23-repository public fleet, then inspect its public pack, Beads work graph, coding-agent routing, review loops, and dated results.

Guide

Gas City Scenarios

See what an open Gas City software factory can do today, from repeatable repository workflows and mixed coding agents to automation, recovery, and reusable packs.

02 / Beads

03 / Learn

Guide

Orchestrating Multiple AI Agents

Learn the architecture needed when multiple AI agents must share work, respect dependencies, recover after failures, and deliver reviewable results.

Guide

Software Factory Reference Architecture

Map the current Gas City factory architecture across customer configuration, Beads work state, workflow control, coding-agent execution, projects, and local observation.

Guide

Enterprise Multi-Agent Orchestration

Learn where Gas City, Beads Team Server, and Gasworks fit when agent work needs team governance, private execution history, and deployment control.

Guide

Software Factory Glossary

Canonical definitions for Beads, Gas City, software factories, work graphs, workflows, agents, local runs, commercial Runs, and related terms.

Guide

Software Factory FAQ

Direct answers about Gas City, Beads, supported coding agents, local execution visibility, team governance, deployment, and how to start.

Guide

The Gas City Product and Community Map

Map the Gas City products and ecosystem: Beads, Gas City, Beads Team Server, Gasworks, the Registry, documentation, GitHub projects, and Discord community.

Guide

Task Management for Coding Agents

Use six practical tests to choose task management for coding agents, from durable work and dependency graphs to atomic claims and vendor neutrality.

Guide

Durable Memory for Coding Agents

Durable coding-agent memory preserves decisions, discoveries, status, and next work outside the session so another agent can resume cleanly.

Guide

Why Coding Agents Need a Work Graph

See how parent-child, blocking, and provenance edges turn coding-agent tasks into a work graph with a continuously updated ready frontier.

Guide

Recover Agent Work After a Crash

Recover coding-agent work after a crash by keeping the job, discoveries, status, and dependencies in a durable Beads work graph.

Guide

When Markdown Todos Stop Working

Replace proliferating agent plan files with queryable work state, explicit dependencies, atomic claims, and durable recovery.

04 / Compare

Comparison

Gas City vs Factory.ai

A factual comparison of Gas City's open software-factory engine and Factory.ai's integrated commercial platform.

Comparison

Agent Orchestration Evaluation Rubric

Evaluate whether a software factory becomes an adaptable capability your team owns, then test its operation under real work and agent failure.

Comparison

Beads vs br

A factual comparison of current Dolt-backed Beads and the classic SQLite-and-JSONL design preserved by br.

Comparison

Beads vs ticket (tk)

A factual comparison of Beads' Dolt-backed work protocol and ticket/tk's compact Markdown task graph.