beads

beads (bd) is a Dolt-backed issue tracker built for agent work. It is how an agent stays on task across context compaction, and how you track what the agent actually did — with dependencies, status, and notes intact sessions later.

Why braynee uses it

Agent task state can't live in prose. It needs structure (dependencies, status), durability (it has to survive compaction and new sessions), and a single source of truth. That's deliberately not Markdown and not the vault — those are for knowledge, not work-in-flight. beads owns the work; the vault owns what you know.

This is the three-way mirror, and the three roles are distinct on purpose:

• beads — the source of truth for agent task state.
• Claude Code's todo list — the live, in-terminal view while you work.
• The vault task view — the same tasks surfaced inside Obsidian via the Dataview and Tasks plugins, for reading next to your notes. braynee syncs it from beads; you read it, you don't hand-edit it.

If you prefer the TaskNotes plugin as your vault-side surface you can wire it yourself, but /braynee:setup does not install it and it isn't required — the shipped vault view is Dataview + Tasks.

How it's set up

bd is a standalone binary with its own release cycle and a server shared across all your projects, so braynee depends on the canonical install rather than vendoring a copy that would fork from your global bd. The setup wizard detects whether bd is present and, if not, offers the install command and runs it on your confirmation.

Connects with

• Tools: synced into the vault view · lives alongside the Obsidian vault
• Concepts: closes The Workflow loop · Architecture — Pillar 2
• Reference: hooks that keep the mirror in sync · task skills