bd is a git-backed issue tracker designed for AI-supervised coding workflows. The harness uses it as the durable task ledger and the memory substrate that survives context resets and compactions.
- Upstream repo: https://github.com/steveyegge/beads
- Documentation: https://steveyegge.github.io/beads/
- Durable state outside the model. Tasks, dependencies, comments, and ready-queues persist across sessions.
- Memory that survives compaction.
bd rememberwrites self-contained insights agents can recall on the nextbd prime. - Multi-agent handoff. Specialist sub-agents claim, comment on, and close tasks without a shared chat history.
curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bashFor macOS / Linux package managers, build-from-source, or air-gapped installs, see the Beads README.
Verify:
bd --versioncd <your-repo>
bd init --prefix <repo>
bd primebd prime is the canonical session-start hook for the harness. Wire it into your runtime's session-start hook so every agent run begins with workflow context, ready tasks, and recent memories already loaded.
bd create "<task title>" -t task -d "<description> [Ticket: <ID>]"
bd ready
bd update <id> --claim
bd comments add <id> "<status>"
bd remember "<learning>" --key <repo>/<prefix>/<topic>
bd close <id> --reason "<reason>"Avoid bd edit — it opens $EDITOR and blocks non-interactive agents. Use bd update <id> --title/--description/--notes instead.
Use self-contained memory text and consistent keys. The full taxonomy lives in core/protocols/bd-and-memory.md.
| Prefix | Use for |
|---|---|
<repo>/decision/<topic> |
Architectural choices and rationale |
<repo>/trouble/<topic> |
Resolved issues with root cause and fix |
<repo>/tool/<topic> |
Tool research outcomes and version notes |
<repo>/lesson/<topic> |
Post-incident or post-task learnings |
<repo>/security/<topic> |
Security findings and CVE notes |
<repo>/perf/<topic> |
Performance findings and benchmarks |
<repo>/pref/<topic> |
User preferences and workflow conventions |
The whole bd story — pre-compact snapshot, in-progress task comments, post-compact prime — is in LIFECYCLE.md.