493b7008a2
The JSONL file hash mismatch warning was appearing consistently after git commit operations, even when no actual data inconsistency existed. Root Cause: Two code paths export to JSONL but only one updated jsonl_file_hash: - flushToJSONLWithState() (used by bd update/create): Updated both jsonl_content_hash AND jsonl_file_hash - finalizeExport() (used by bd sync --flush-only): Updated only jsonl_content_hash, NOT jsonl_file_hash Since validateJSONLIntegrity() checks jsonl_file_hash, any bd command after a git commit would see a mismatch and trigger the warning. Steps to Reproduce (before fix): 1. cd /path/to/beads-project 2. bd update -p 3 some-issue-id # Works fine, stores hash H1 3. git add .beads/issues.jsonl && git commit --amend --no-edit # Pre-commit hook runs bd sync --flush-only # This updates jsonl_content_hash to H2 but leaves jsonl_file_hash as H1 4. bd update -p 3 some-issue-id # WARNING appears! # validateJSONLIntegrity() compares file (H2) with jsonl_file_hash (H1) 5. Repeat steps 3-4 indefinitely - warning always appears The fix adds SetJSONLFileHash() call to finalizeExport(), ensuring both export paths update the same metadata consistently.
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.
