Beads

Beads, installed as the bd command, is an open-source issue tracker and memory layer designed for AI coding agents. Instead of storing plans in scattered markdown files, Beads gives a project a structured graph of issues, dependencies, messages, memories, and audit history. The README describes it as a distributed graph issue tracker powered by Dolt, with support for macOS, Linux, Windows, and FreeBSD. For teams using Claude Code, Codex, Factory Droid, Cursor, or other coding agents, the main promise is persistent project context that survives across sessions and branches. The normal workflow starts with installing the CLI, running bd init inside a project, and letting Beads create or update agent instructions such as AGENTS.md. From there, agents and humans can use commands like bd ready to list unblocked work, bd show to inspect an issue, bd update --claim to atomically claim a task, bd dep add to link dependencies, bd close to finish work, and bd remember to store long-lived project memory. The project also includes setup helpers for agent environments, including bd setup codex, bd setup claude, and bd setup factory. Beads is useful when agent work starts to outgrow simple TODO lists. A single task can have blockers, relationships, child tasks, messages, and memories. Because the data sits in a version-controlled Dolt database, it is built for multi-branch and multi-agent development where merge conflicts and lost context are common failure modes. The README calls out hash-based IDs, dependency tracking, auto-ready detection, JSON output, semantic memory compaction, graph links, and threaded messages. Those details make it especially relevant to coding-agent workflows where tools need machine-readable state, not prose buried in a planning document. Pricing is simple for the open-source project: the repository and packages are available without a paid SaaS requirement. Teams may still incur their normal infrastructure or storage costs if they sync Dolt remotes or build custom hosting around it. Beads should be considered by developers who want agents to coordinate around explicit tasks, blockers, memories, and handoffs. It is not a replacement for a full product-management suite; it is a compact, agent-friendly project memory system that works close to the codebase. The main tradeoff is that Beads asks a team to adopt a specific workflow and command set. That is a good fit when agents need clear state, but it may feel heavy for a tiny project with one developer and a short task list. It works best when the repository is already the center of work and the agent needs to understand which issues are ready, claimed, blocked, or remembered. Because the project exposes structured commands, it also gives humans an audit trail when agents make progress or change direction.