4ccdd7a2df
* fix(routing): close original store before replacing with target store Fix "database is closed" error during auto-flush when contributor routing redirects issue creation to a different repository (e.g., ~/.beads-planning). When a user is detected as a contributor (based on git remote URL pattern), the default configuration routes new issues to ~/.beads-planning instead of the current repository. This routing caused auto-flush to fail with: Warning: auto-flush failed: failed to get stored JSONL hash: failed to get jsonl_file_hash: sql: database is closed In create.go, when switching to the planning repo: 1. targetStore was opened for the planning database 2. A defer was set to close targetStore at function end 3. store = targetStore replaced the global store pointer 4. Issue was created successfully 5. Command Run ended → defer closed targetStore 6. PersistentPostRun tried to flush using the global store → error! The bug: the defer closed targetStore, but the global `store` variable pointed to the same object. When PersistentPostRun called flushManager.Shutdown(), it tried to use the already-closed store for the flush operation. - Remove the defer that prematurely closed targetStore - Explicitly close the ORIGINAL store before replacing it (it won't be used) - Let PersistentPostRun close whatever store is current at exit time This ensures proper store lifecycle: - Original store: closed when replaced (no longer needed) - Target store: closed by PersistentPostRun after flush completes 1. Have a git repo with a remote URL that doesn't match maintainer patterns (e.g., github-a:org/repo.git instead of git@github.com:org/repo.git) 2. Have ~/.beads-planning directory with beads initialized 3. Run: cd /path/to/repo && bd create "Test issue" 4. Observe: Issue created successfully, but followed by: Warning: auto-flush failed: ... sql: database is closed Added debug prints to SQLiteStorage.Close() and GetJSONLFileHash() which revealed two different databases were involved: - /path/to/repo/.beads/beads.db (closed first, unexpectedly) - ~/.beads-planning/.beads/beads.db (used for flush after being closed) * fix(test): resolve race condition in TestAutoFlushOnExit Not directly related to the previous routing fix, but exposed by CI timing. Root cause: The test had a latent race condition between two channel operations: 1. markDirtyAndScheduleFlush() sends event to markDirtyCh 2. Shutdown() sends request to shutdownCh Without any delay, Go's scheduler might process the shutdown event first. Since isDirty was still false (markDirty event not yet processed), the FlushManager would skip the flush entirely, causing the test to fail with "Expected JSONL file to be created on exit". The race was always present but only manifested in CI environments with different timing characteristics (CPU contention, virtualization, scheduler behavior). Fix: Add a 10ms sleep after markDirtyAndScheduleFlush() to allow the FlushManager's background goroutine to process the event before shutdown. This mimics real-world behavior where there's always some time between CRUD operations and process exit.
bd - Beads
Distributed, git-backed graph issue tracker for AI agents.
Beads provides a persistent, structured memory for coding agents. It replaces messy markdown plans with a dependency-aware graph, allowing agents to handle long-horizon tasks without losing context.
⚡ Quick Start
# Install (macOS/Linux/FreeBSD)
curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Initialize (Humans run this once)
bd init
# Tell your agent
echo "Use 'bd' for task tracking" >> AGENTS.md
🛠 Features
- Git as Database: Issues stored as JSONL in
.beads/. Versioned, branched, and merged like code. - Agent-Optimized: JSON output, dependency tracking, and auto-ready task detection.
- Zero Conflict: Hash-based IDs (
bd-a1b2) prevent merge collisions in multi-agent/multi-branch workflows. - Invisible Infrastructure: SQLite local cache for speed; background daemon for auto-sync.
- Compaction: Semantic "memory decay" summarizes old closed tasks to save context window.
📖 Essential Commands
| Command | Action |
|---|---|
bd ready |
List tasks with no open blockers. |
bd create "Title" -p 0 |
Create a P0 task. |
bd dep add <child> <parent> |
Link tasks (blocks, related, parent-child). |
bd show <id> |
View task details and audit trail. |
🔗 Hierarchy & Workflow
Beads supports hierarchical IDs for epics:
bd-a3f8(Epic)bd-a3f8.1(Task)bd-a3f8.1.1(Sub-task)
Stealth Mode: Run bd init --stealth to use Beads locally without committing files to the main repo. Perfect for personal use on shared projects.
📦 Installation
- npm:
npm install -g @beads/bd - Homebrew:
brew install steveyegge/beads/bd - Go:
go install github.com/steveyegge/beads/cmd/bd@latest
Requirements: Linux, FreeBSD, macOS, or Windows.
🌐 Community Tools
See docs/COMMUNITY_TOOLS.md for a curated list of community-built UIs, extensions, and integrations—including terminal interfaces, web UIs, editor extensions, and native apps.
