How to Use It Well
- Setup time ~12 minutes (install CLI +
bd initin one repo) - Persistent graph beats markdown plans for long-horizon work (dependencies, status, claims)
- GitHub stars + forks (verified): see Source & Thanks
Treat memory as a data structure, not prose. If an agent can query a graph (what’s blocked, what’s claimed, what changed), it can plan more reliably and avoid re-deriving the same context every run.
FAQ
Q: Do I need to clone the repo into my project? A: No. The README recommends installing the CLI system-wide and using it across repos.
Q: What’s the first command to learn?
A: bd prime (or equivalent) to get workflow context, then bd show/update/close for issue lifecycle.
Q: Is it tied to one agent? A: No. The README mentions multiple integrations (Codex, Claude, Cursor, etc.); use the setup that matches your tool.