Continue the conversation — chat opens pre-seeded with the current signal, caps, and movement.
Git-backed, dependency-graph issue tracker that gives AI coding agents persistent memory across sessions, branches, and machines. Created and maintained by Steve Yegge; the repository was renamed from steveyegge/beads to gastownhall/beads (the GitHub org that also hosts Gas Town and Gas City), with canonical docs at gastownhall.github.io/beads.
Target user: individual developers and small teams using agentic coding tools (Claude Code, Codex CLI, Cursor, Windsurf, Sourcegraph Amp) who have hit the limit of session-scoped context. Beads is infrastructure for agents, not a tool for end-users directly.
Differentiator: a Dolt-backed versioned dependency DAG with semantic compaction and targeted queries (bd ready); git-native with hash-based IDs that survive merges; an official MCP server (beads-mcp). Yegge has publicly reframed Beads as a protocol/discovery ('an interface, not a single implementation') and endorsed a Rust port (beads_rust) that freezes the older SQLite+JSONL 'Beads Classic' architecture — reducing single-implementation lock-in and offering an escape hatch from the Dolt migration's instability.
Adoption & Proof Points
- **GitHub stars:** 24.18k (up from 23.8k baseline; ~1.6% over ~11 days — growth continuing but decelerating from the prior ~16%/mo)
- **Forks:** 1.6k; **Open issues:** ~377 (elevated, consistent with the v1.0/Dolt-migration churn)
- **Release cadence:** v1.0.0 shipped Apr 2, 2026 (Dolt migration complete); v1.0.4 shipped May 9, 2026 (reliability hardening); repo pushed daily
- **Contributors:** 100+, though Yegge-concentrated (4,554 commits vs #2's ~500); Yegge reports ~50 PRs/day
- **Ecosystem breadth:** 20+ ecosystem tools; six external tracker integrations (Jira, Linear, Azure DevOps, GitLab, Notion, GitHub Issues); Dolt peer-to-peer federation; endorsed Rust port (beads_rust); DoltHub-restored 'Beads Classic'; downstream Gas City enterprise-grade SDK built on the Beads+Dolt MEOW stack
- **Official MCP server** on PulseMCP (beads-mcp PyPI, FastMCP 2.13.0); npm distribution (@beads/bd)
- No named enterprise customers; no commercial revenue; no funding for Beads itself
Risks & Limitations
- **no-enterprise-features cap active:** all dimensions capped at 14 (Context pinned exactly at 14); this is the binding constraint preventing advancement to Assessed
- **Solo-leaning maintainer bus factor:** Yegge dominates commits; no funding, no company, no organizational backstop for Beads itself (Gas City is a separate downstream effort)
- **v1.0 Dolt-migration reliability turbulence:** documented data-loss incidents (#2573 'made beads unusable' [closed], #2363 247-issue destruction [open], #2276/#2433 migration failures); largely mitigated by v1.0.1-1.0.4 but #2363 not formally closed
- **Invasiveness criticism:** auto git-push behavior (which Yegge himself reports he cannot fully suppress) and 'written by AI for AI' DX taste critique persist
- **Agent reliability ceiling:** agents do the right thing ~80% of the time and drop bd usage during long sessions (context rot), requiring human supervision
- **GAS-token reputational footnote:** Jan 2026 third-party Solana meme coin on the 'Gas Town' name that Yegge briefly endorsed then disavowed (-98%); ecosystem-level, not a Beads product issue, and now receded
- **Competitive/fork pressure:** claude-mem, agentmemory, and native CLAUDE.md memory compete; PaiR and beads_rust fork off Beads (beads_rust is Yegge-endorsed; PaiR is niche off the old 0.49.x architecture)
Capabilities & Integration
**Autonomy (9): ** passive data store agents query via CLI or MCP. Beads itself does not plan or execute. Value-add for agents: dependency tracking, semantic compaction, bd ready for prioritized work surfacing. ~80% reliable in practice; needs light human supervision.
**Integration (12, Team-Aware floor):** git-native with hash-based IDs preventing merge conflicts. Six tracker integrations (Jira, Linear, Azure DevOps, GitLab, Notion, GitHub Issues). Dolt peer-to-peer federation for cross-machine state. No PR-workflow or Slack/Teams integration.
**Context (14, Repository-Deep at cap):** best-in-class at project-level persistent memory across sessions, branches, and machines via a Dolt-backed versioned dependency graph. Manages task/project context — not code semantic context (no code indexing).
**Interface (11, Dual-Mode): ** bd CLI primary (JSON output) plus an official MCP server (beads-mcp, FastMCP 2.13.0). Claude Code plugin, npm (@beads/bd), one-click MCP setup. Community UIs (beads-ui, beads_viewer, BeadHub, BeadBoard) are unofficial.