B

Beads

A Dolt-powered dependency graph that gives coding agents persistent memory

PriceOpen SourceReviewed2026-04-26
Verdict — Ship
3 Ships1 Skips
Visit github.com

The Panel's Take

Beads (bd) is an open-source distributed graph issue tracker built specifically for AI coding agents. Rather than relying on fragile markdown plans or context-window hacks, Beads gives agents a Dolt-powered SQL database with native branching, cell-level merging, and dependency-aware task graphs — so they can track complex multi-step work without losing the thread. At its core, Beads replaces the ad-hoc "write a plan.md" pattern with a real structured store. Agents create tasks, set dependencies, claim work atomically, and receive semantic "memory decay" compaction that summarizes completed tasks to keep context windows lean. Hash-based IDs (e.g. bd-a1b2) prevent merge collisions across multi-agent, multi-branch workflows. The v1.0 milestone, released in April 2026, signals production stability. With 21.5k GitHub stars, Homebrew and npm distribution, and support across macOS, Linux, Windows, and FreeBSD, Beads is rapidly becoming the default memory layer for teams running agent swarms that need to coordinate without stepping on each other.

Share this verdict

Beads verdict: SHIP 🚀

3 ships · 1 skip from the expert panel

Full review: shiporskip.io/tool/beads-gastownhall-graph-issue-tracker-coding-agents-dolt-2026

Weekly AI Tool Verdicts

Get the next verdict in your inbox

7 critics review a new AI tool every day. Weekly digest — free.

Embed this verdict

Tool makers can add a live ShipOrSkip badge to their site. Badge loads track impressions; clicks route back to this review.

Ship · 7.5/10
HTML badge
<a href="https://shiporskip.io/api/badge-click/beads-gastownhall-graph-issue-tracker-coding-agents-dolt-2026" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/beads-gastownhall-graph-issue-tracker-coding-agents-dolt-2026" alt="Beads Ship verdict on ShipOrSkip" width="360" height="90" /></a>
Markdown badge
[![Beads Ship verdict on ShipOrSkip](https://shiporskip.io/api/badge/beads-gastownhall-graph-issue-tracker-coding-agents-dolt-2026)](https://shiporskip.io/api/badge-click/beads-gastownhall-graph-issue-tracker-coding-agents-dolt-2026)
Iframe widget
<iframe src="https://shiporskip.io/embed/beads-gastownhall-graph-issue-tracker-coding-agents-dolt-2026" title="Beads ShipOrSkip verdict" width="360" height="260" style="border:0;border-radius:16px;max-width:100%;" loading="lazy"></iframe>

The reviews

This solves a real pain point I hit every time I run multi-agent loops — agents clobbering each other's work. Dolt as the backend is smart: you get SQL semantics, branching, and merge without standing up anything exotic. The `bd ready` command alone justifies the install.

Helpful?

Dolt is a dependency most teams haven't heard of, and 'distributed SQL for your coding agent' is a steep onboarding curve for what is essentially a task tracker. If your agent loop is simple enough, a JSON file in the repo still beats this. Wait for the ecosystem to mature.

Helpful?

The shift from 'agent with a scratchpad' to 'agent with a version-controlled, branching task graph' is significant. Beads is early infrastructure for the multi-agent software factory — the kind of coordination layer that will be table stakes in 18 months.

Helpful?

As someone who runs Claude Code sessions for creative pipelines, the semantic memory compaction is the killer feature — it means long projects don't have to start fresh every session. The CLI UX is clean too.

Helpful?

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later