braid
A local-first issue tracker for LLM agents (and the humans they work with).
braid stores a project’s issues in a skein: a single automerge CRDT document, synced through an automerge sync server. A single issue is a strand (full vocabulary: terminology). There is no git involvement and no daemon: any number of agents across machines, branches, and worktrees can create, edit, and close strands in parallel — replication and conflict resolution come from the CRDT, not from merge tooling.
braid is heavily inspired by beads:
it borrows the issue shape, dependency types, and ready/blocked workflow,
while replacing the git-committed issues.jsonl + SQLite machinery with a
synced document. (That JSONL file still matters: braid import migrates
it.)
Where to next
- New here? Install braid, then walk the quick start.
- Running it for real? Read the document id is a secret — the doc id is a bearer token — and point braid at your own configuration.
- Wiring up an agent? Shell-capable agents use the CLI (
braid agents-info); shell-less ones use the MCP server. - Coming from beads? See migrating from beads.