- Go 95.2%
- Python 1.6%
- Starlark 1.5%
- Shell 1.3%
- Rust 0.2%
* fix(test): remove t.Parallel() from cobra Help tests to fix data race cobra's OutOrStdout() eagerly evaluates os.Stdout as the default argument even when cmd.SetOut() has been called, so any parallel test calling cmd.Help() or cmd.Execute() races with captureStdout() which redirects os.Stdout behind stdioMutex. Remove t.Parallel() from the three TestSearchCommand_* tests that exercise this path. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * test: add cobra-parallel policy guard and stdio mutex contract test - TestCobraParallelPolicyGuard: scans test files and fails if any parallel test calls cobra Help()/Execute() without SetOut/SetErr. Strips comments to avoid false positives. - TestStdioMutexContract: deterministic reentrancy check proving stdioMutex serializes captureStdout calls (fails without -race). - Update stdioMutex documentation to explain that SetOut is NOT sufficient to prevent the race (cobra eagerly reads os.Stdout). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * refactor(test): strengthen cobra-parallel policy guard Remove the SetOut/SetErr escape hatch since cobra's OutOrStdout() eagerly evaluates os.Stdout even when outWriter is set. The guard now forbids ALL cobra output methods in parallel tests. Also adds stripStringLiterals() to prevent self-matching false positives. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .agent/workflows | ||
| .beads | ||
| .beads-hooks | ||
| .claude | ||
| .claude-plugin | ||
| .devcontainer | ||
| .github | ||
| claude-plugin | ||
| cmd/bd | ||
| docs | ||
| examples | ||
| integrations | ||
| internal | ||
| npm-package | ||
| scripts | ||
| tests/integration | ||
| website | ||
| winget | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .goreleaser.yml | ||
| .pre-commit-config.yaml | ||
| .test-skip | ||
| AGENT_INSTRUCTIONS.md | ||
| AGENTS.md | ||
| ARTICLES.md | ||
| beads.go | ||
| beads_test.go | ||
| BENCHMARKS.md | ||
| build-docs.md | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| codecov.yml | ||
| CONTRIBUTING.md | ||
| default.nix | ||
| FEDERATION-SETUP.md | ||
| flake.lock | ||
| flake.nix | ||
| go.mod | ||
| go.sum | ||
| install.ps1 | ||
| LICENSE | ||
| Makefile | ||
| NEWSLETTER.md | ||
| README.md | ||
| RELEASING.md | ||
| SECURITY.md | ||
| THIRD_PARTY_LICENSES | ||
bd - Beads
Distributed, git-backed graph issue tracker for AI agents.
Platforms: macOS, Linux, Windows, FreeBSD
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 beads CLI (system-wide - don't clone this repo into your project)
curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Initialize in YOUR project
cd your-project
bd init
# Tell your agent
echo "Use 'bd' for task tracking" >> AGENTS.md
Note: Beads is a CLI tool you install once and use everywhere. You don't need to clone this repository into your project.
🛠 Features
- Dolt-Powered: Version-controlled SQL database with cell-level merge and native branching. JSONL maintained for git portability.
- 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. - Compaction: Semantic "memory decay" summarizes old closed tasks to save context window.
- Messaging: Message issue type with threading (
--thread), ephemeral lifecycle, and mail delegation. - Graph Links:
relates_to,duplicates,supersedes, andreplies_tofor knowledge graphs.
📖 Essential Commands
| Command | Action |
|---|---|
bd ready |
List tasks with no open blockers. |
bd create "Title" -p 0 |
Create a P0 task. |
bd update <id> --claim |
Atomically claim a task (sets assignee + in_progress). |
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.
Contributor vs Maintainer: When working on open-source projects:
- Contributors (forked repos): Run
bd init --contributorto route planning issues to a separate repo (e.g.,~/.beads-planning). Keeps experimental work out of PRs. - Maintainers (write access): Beads auto-detects maintainer role via SSH URLs or HTTPS with credentials. Only need
git config beads.role maintainerif using GitHub HTTPS without credentials but you have write access.
📦 Installation
- npm:
npm install -g @beads/bd - Homebrew:
brew install beads - 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.