Updated

Beads

An open-source (MIT) issue tracker for coding agents, the `bd` CLI, that stores dependency-linked issues in a version-controlled Dolt database so agents can pick up unblocked work and keep their plan across context resets.

7 open-source projects declare Beads in their code; no maker's live product we track uses it yet.

Open sourceSelf-hostableFree tier

Profile checked

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

How makers use Beads

What Beads is used for

Context & Skills for Coding Agents · Memory and tasks →An issue tracker the agent reads and writes through the `bd` CLI, keeping dependency-linked tasks in a version-controlled Dolt database so its plan survives context resets.Trade-off: Another CLI and database in the loop; listed in full under Parallel Agents & Spec-Driven Work.
Parallel Agents & Spec-Driven Work · Spec-driven method →An issue tracker built for agents — the `bd` CLI keeps dependency-linked issues in a version-controlled Dolt database, so agents can find unblocked work and keep their plan across context resets.Trade-off: Another database and CLI for the agent to learn, and a recent storage migration means older guides may not match.
Conductor23Superset8ccusage1Claude Squad0Nimbalyst0Beads0Makers' products on each, for parallel agents & Spec-Driven work

Beads vs the alternatives makers chose

OptionMakers' productsTeam of 5, 10,000 usersOpen source
Conductor23 72%$250/mo · ProNo
Superset8 25%—No
ccusage1 3%—Yes
Beads0 0%—Yes

For parallel agents & Spec-Driven work: how many of the 32 makers' products we know the parallel agents & Spec-Driven work of chose each option, and what each costs for a team of 5 with 10,000 users.

Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for.

When to use Beads, and when not

Something else fits better if

  • You use Claude Code or Codex on a Mac and want several tasks running at once, each in its own copy of the repo: Conductor or Superset.
  • You live in the terminal and want parallel agents with free, open-source tooling: Claude Squad.
  • You want the agent to write a spec and plan you approve before it codes, inside the agent you already use: Spec Kit or OpenSpec.
  • You want plans and specs written as tickets that any agent can then pick up: Traycer.
  • You want to follow and answer your agents from your phone while away from the desk: Happy.
From each decision's guide, written from what makers' products chose and why.

How Beads itself is built

4 tools, from its own code, website and Product Hunt page.

Who uses it

No maker's live product on record yet, and 7 open-source projects that declare it in their code.

We haven't found a maker's live product that uses Beads yet — only the open-source projects below, which declare it in their code.

Open source: a project that declares Beads as a dependency in its public code — verifiable, but not necessarily a live product.

Questions makers ask about Beads

What are the alternatives to Beads?

For parallel agents & Spec-Driven work, the other options makers' products we track chose most are Conductor (23), Superset (8), ccusage (1). Open source or self-hostable among them: ccusage. Each alternative, with the situation it fits, is on the Beads alternatives page.

Is Beads free?

Yes — it is free, open-source software.

Is Beads open source or self-hostable?

Open source, and you can self-host it. source ↗

Can AI coding agents work with Beads?

No llms.txt, official MCP server or CLI found yet.

Who uses Beads?

No maker's live product we track yet; 7 open-source projects declare it in their code. source ↗