Beads CLI
The bd issue tracker with a dependency graph on Dolt: long-term memory and a work plan for agents instead of Markdown lists
- 28,281 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Edits AGENTS.md and installs agent hooks in the project
- Syncs the task database with a git remote
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/beadsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Edits AGENTS.md and installs agent hooks in the project
- Syncs the task database with a git remote
This is third-party code. Review the repository files before installing.
What it does
Beads stores project tasks in a versioned Dolt SQL database and links them with dependencies, so the agent can see what is ready to pick up. bd ready lists work with no open blockers, bd update --claim assigns a task to the agent, and bd close finishes it and unblocks dependents. Hash-based IDs avoid collisions when several agents and branches work in parallel. Old closed tasks are compacted into short summaries, and bd remember saves project knowledge that bd prime feeds to the agent at session start.
Who it is for. For developers who run long multi-session tasks with agents or several agents in parallel.
Good fit when
- The agent loses the plan between sessions
- Several agents work on one project and need to share tasks
- You want task history and project knowledge next to the code
Not a fit when
- The team already tracks work in Jira, Linear or another tracker and does not want a second system
- Short one-off tasks where the plan fits in one session
Example request
Break the migration into beads tasks with dependencies and claim the first ready oneLimitations
Storage is Dolt: the default mode has a single writer, concurrent writers need a separate dolt sql-server. Upgrades across schema versions on a shared database require the steps from the upgrade guide. bd init edits AGENTS.md and installs Claude and Codex integrations by default, which --skip-agents or --stealth turn off.
How to disable. Remove the beads section from AGENTS.md and the hooks added by bd setup, then uninstall with brew uninstall beads or npm uninstall -g @beads/bd. Data lives in the project's .beads folder.
FAQ
Is git required?
No. With BEADS_DIR and --stealth beads runs without git, keeping the Dolt database separate.
How do I sync tasks across machines?
With bd dolt push and bd dolt pull against the same git remote. issues.jsonl is an export, not a backup.
Discussion
No questions or reviews yet.
Related
CLI toolsA Rust terminal task board: every task runs in its own git worktree and tmux window while Claude Code, Codex, Gemini CLI and other agents work in parallel
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
Guild keeps tasks, knowledge and handoff notes between sessions in local SQLite so Claude Code, Codex and Cursor share context
A Rust CLI that builds a knowledge graph of code and decisions and feeds the agent the right slice through Claude Code hooks
A portable .agent folder with memory, skills and protocols that plugs into many coding agents and keeps its knowledge when you switch tools
A desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
README in short
The README describes beads as a distributed issue tracker for agents built on Dolt. Install via Homebrew, npm, a script or go install, then run bd init in the project and bd setup for your agent. It lists core commands, hierarchical IDs for epics, storage modes, sync and git-free usage. It also covers binary checksum verification and the schema version guard. MIT licensed.