beads

Track cross-session work with a git-backed persistent memory for Beads.

26|3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/thoreinstein/gemini-beads --skill beads-thoreinstein
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/thoreinstein/gemini-beads/tree/main/skills/beads
Command: npx skills add https://github.com/thoreinstein/gemini-beads --skill beads-thoreinstein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides a git-backed memory for multi-session work, enabling persistent context across conversations, blockers, and compaction cycles so teams can resume where they left off without losing critical decisions.

Core Features & Use Cases

  • Persistent memory across compaction and sessions for multi-step work
  • Graph-based issue tracking with dependency types like blocks, related, parent-child, and discovered-from
  • Git-backed issues with syncing and history
  • Support for molecules (protos), wisps, and planned workflows
  • Useful for knowledge work, debugging, and long-running projects

Quick Start

Create a beads issue and start a session with bd ready to surface work.

Frequently Asked Questions about beads

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist task context across multiple sessions when conversation compaction loses my notes?▼

You can persist multi-session task context using a git-backed memory that stores long-running decisions in notes, ensuring critical information survives conversation compaction cycles without losing progress.

What is the best way to track cross-session task dependencies like blockers and parent-child relationships?▼

Tracking cross-session task dependencies is handled through a graph-based issue tracker that enforces dependency types including blocks, related, parent-child, and discovered-from, enabling structured workflow management across sessions.

How do I start a work session and surface relevant tasks from my git-backed issue tracker?▼

To start a session and surface work, create a beads issue first, then run the ready command to automatically surface relevant pending tasks and blockers from your git-backed persistent memory.

Can I sync issue tracking history across a team using a git-backed memory approach?▼

Yes, git-backed issue tracking provides built-in syncing and history through version control, allowing teams to coordinate multi-session work and maintain a shared record of decisions and blockers.

Does this persistent memory tool support complex workflows involving molecules and wisps?▼

The persistent memory tool supports molecules (protos), wisps, and planned workflows, allowing teams to structure complex debugging and knowledge work tasks across long-running projects.

Why do I lose critical project decisions when resuming work after a conversation compaction?▼

Critical project decisions are lost during compaction because standard session memory is volatile, whereas git-backed persistent notes store these decisions externally to ensure seamless work resumption.