Beads Persistent Task Graph FAQs

Question 1

How does Beads handle Claude's context limits?

Accepted Answer

Beads stores task data in a local database that survives compaction events, allowing Claude to reconstruct the full project state even after the conversation history is cleared.

Question 2

What happens to my tasks after a compaction event?

Accepted Answer

While conversation history is lost during compaction, all Beads data—including issue status, notes, and dependencies—remains intact, serving as the agent's primary memory for recovery.

Question 3

Does Beads require a central server?

Accepted Answer

No, Beads is git-backed and uses a local .beads/ directory or a global ~/.beads/ database to store all information locally on your machine.

Question 4

When should I use Beads instead of a simple todo list?

Accepted Answer

Use Beads for multi-session work with complex dependencies or fuzzy boundaries. Use simple todo lists for linear, straightforward tasks that will be completed in a single session.

Question 5

Can I use Beads across different projects?

Accepted Answer

Yes. Beads automatically detects project-local databases in your current directory but can fall back to a global database for cross-project tracking and personal knowledge work.

Beads Persistent Task Graph

Key Features

Use Cases

Beads Persistent Task Graph

Key Features

Use Cases