An SDK from the Gas Town team for building multi-agent coding workflows from formulas, sessions and a Beads data plane.
The summary describes what the project says it does; inclusion is not an endorsement.
The first-party successor to Gas Town, not an independent fork.
github.com · Issue #209, Problem
“Retries restart from a moving HEAD, dependent members can miss predecessor source, independent outputs reach review without integration, and approval can detach from the published commit.”
Tie review to the exact commit that ships, and invalidate the approval when a fix changes that commit.
github.com · Issue #1709
“A convoy of 5 implementation beads produces 5 separate runs, each walking the full formula: implement, review, check architecture, verify coverage. That means 5 separate reviews that each see only their own fragment”
The proposal: fan out the implementation, then review the whole convoy as one artifact. It's a proposal, not a report of a broken feature.
github.com · Issue #1052
“Both sessions execute the same step. The losing session does not detect that it lost the claim — it had already started before the winning session's claim was persisted.”
An atomic claim isn't enough on its own. A worker must check that it won before it starts. Closed in June 2026.
github.com · Issue #2987
“bd list over the molecule's 50 step beads reported open=50, in_progress=0, closed=0 — zero progress reflected in the cached read.”
A shared database can still give two answers: cached list reads lagged the store by minutes. Open, with the cause suspected but not confirmed.
medium.com · Pull quote under the subtitle
“A durable work record is not the same thing as a durable procedure.”
A task that survives a crash in the tracker can still lose the process working on it. She has contributed hundreds of PRs to Gas City and runs it on itself.
medium.com · When a town won’t stay lit
“Because every dispatch reparsed the entire file under a lock, order firing froze. One wedged session claimed the same bead ten times over 5.6 hours.”
About 100 patrol and repair jobs were firing roughly 850 times an hour. The store had grown to 168 MB with 79,210 beads, 96% of them closed.
medium.com · The task survived. The procedure did not.
“It can launch another agent and leave two processes editing the same worktree.”
What a naive retry does after the coordinator dies mid-handoff. She also lists stranded claims, duplicate sessions after retries and stale completions arriving after a newer generation started.