Beads FAQs

Question 1

What does the Beads skill do for Claude Code?

Accepted Answer

Beads (bd) is a graph-based issue tracker that provides Claude with persistent memory. It allows the AI to track complex coding tasks, dependencies, and progress notes in a database that survives even when the conversation history is cleared or compacted.

Question 2

What are the core features of the Beads graph-based tracker?

Accepted Answer

Beads supports hierarchical dependency tracking (blocking/related tasks), structured progress checkpointing (Completed, In-Progress, Blockers, Next Steps), automatic database discovery (project-local or global fallback), and JSON output for programmatic integration.

Question 3

Does Beads require manual configuration for different projects?

Accepted Answer

No. Beads automatically discovers its database. It looks for a .beads/ directory in your current project for specific work, and falls back to a global database in your home directory (~/.beads/) for cross-project tasks or general knowledge work.

Question 4

How does Beads help Claude survive conversation compaction?

Accepted Answer

Claude's conversation context is limited; once full, it 'compacts' and forgets previous history. Beads stores data in a local or global database (.beads/) outside the chat window. By running 'bd show', Claude can reconstruct its full technical context and resume work exactly where it left off.

Question 5

When should I use Beads instead of TodoWrite?

Accepted Answer

Use Beads for multi-session work, tasks with complex dependencies (blockers/parent-child), or exploratory 'side quests' that span several days. Use TodoWrite for simple, linear checklists that will be completed within a single chat session.

Beads

Beads

Key Features

Use Cases

Key Features

Use Cases