Branch data as well as code
Explore ways to copy, diff, and reconcile database or data-lake state per task.
Trade-off: Diverged data eventually needs a reconciliation policy.
Git-like branching, diffing, and merging for SQL database state.
The summary describes what the project says it does; inclusion is not an endorsement.
Explore ways to copy, diff, and reconcile database or data-lake state per task.
Trade-off: Diverged data eventually needs a reconciliation policy.
Isolation creates exploration freedom; the unresolved problem is bringing successful changes back.
Trade-off: The difficult boundary moves to reintegration.
github.com · Problem Statement, item 1
“Workers can't see each other's beads. A bead created by agent A is invisible to agent B until A's branch merges to main.”
Giving each worker its own branch let them write without contention, but they couldn't coordinate. The design doc moved everything to one shared main with explicit transactions, live since 24 February 2026.
steve-yegge.medium.com · Beads: Ready for v1
“The inherent fragility of the v0.x Beads architecture, with its bidirectional sync, 3-way merge, two sources of truth, race conditions, and tombstone hell — that's all gone now.”