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.
The Gas City Guide
Evergreen notes on software factories, multi-agent orchestration, durable agent work, and how Gas City and Beads fit beside the tools teams already use.
Guide
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
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 coding agents with explicit Beads work, blocking dependencies, isolated worktrees, repeatable Gas City workflows, and a human review gate.
Guide
See how Gas City routes one Beads work graph through Claude Code, Codex, Gemini CLI, and other configured coding-agent harnesses.
Guide
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
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.
Guide
Meet Beads, the open protocol and durable work graph that gives coding agents memory across sessions, crashes, compaction, and handoffs.
Guide
Use Jira, Linear, or GitHub Issues for organizational visibility and Beads as the coding agent's local system of action.
Guide
Test whether a coding agent recognizes Beads in a clean project, see what official setup adds, and record a reproducible result.
Guide
Learn the architecture needed when multiple AI agents must share work, respect dependencies, recover after failures, and deliver reviewable results.
Guide
See how Beads and Gas City provide two starting paths toward Beads Team Server and the shared Gasworks factory.
Guide
Understand the difference between an agent framework you code with and a software factory your engineering team operates.
Guide
Separate durable Beads work, Gas City local execution visibility, and the retained operational record provided by Beads Team Server.
Guide
Map the current Gas City factory architecture across customer configuration, Beads work state, workflow control, coding-agent execution, projects, and local observation.
Guide
Learn where Gas City, Beads Team Server, and Gasworks fit when agent work needs team governance, private execution history, and deployment control.
Guide
Canonical definitions for Beads, Gas City, software factories, work graphs, workflows, agents, local runs, commercial Runs, and related terms.
Guide
Direct answers about Gas City, Beads, supported coding agents, local execution visibility, team governance, deployment, and how to start.
Guide
Map the Gas City products and ecosystem: Beads, Gas City, Beads Team Server, Gasworks, the Registry, documentation, GitHub projects, and Discord community.
Guide
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 coding-agent memory preserves decisions, discoveries, status, and next work outside the session so another agent can resume cleanly.
Guide
See how parent-child, blocking, and provenance edges turn coding-agent tasks into a work graph with a continuously updated ready frontier.
Guide
Recover coding-agent work after a crash by keeping the job, discoveries, status, and dependencies in a durable Beads work graph.
Guide
Replace proliferating agent plan files with queryable work state, explicit dependencies, atomic claims, and durable recovery.
Comparison
A factual comparison of Gas City's open software-factory engine and Factory.ai's integrated commercial platform.
Comparison
A factual comparison of Gas City's open execution engine and 8090's collaborative requirements-to-code control plane.
Comparison
Evaluate whether a software factory becomes an adaptable capability your team owns, then test its operation under real work and agent failure.
Comparison
Compare vendor-neutral systems built to preserve durable coding-agent work.
Comparison
A factual comparison of current Dolt-backed Beads and the classic SQLite-and-JSONL design preserved by br.
Comparison
A factual comparison of Beads' Dolt-backed work protocol and ticket/tk's compact Markdown task graph.