v1.0.0
rhizome-mcp is a local-first MCP server for task tracking and coordination of autonomous AI coding agents: one static Go binary, one SQLite database per project, no accounts, no Docker, no network dependency. This is the first stable release — the MCP tool contract, the domain model, and the logical interchange format are now covered by semantic versioning.
Highlights
Coordination built for how agents actually fail. Issues are claimed atomically with renewable leases; in_progress is derived from an active lease, never stored, so a crashed or vanished agent can't lock an issue forever. At most one active attempt per issue is guaranteed at the database level. Checkpoints, supersedable decision records, and an append-only event history let a fresh session resume from the last known-good state.
A 31-tool MCP surface with token budgets as part of the contract. Compact list projections (a 100-issue page stays under 64 KB, enforced by an integration test), graph nodes that exclude free-text bodies at the SQL layer, snippet-only search (SQLite FTS5), delta sync via event IDs, and a bounded single-call work-context package. Optimistic versioning, replay-safe idempotency keys, and 19 stable machine-readable error codes throughout.
Planning, dependencies, and review. Epics, labels, cycle-checked blocks relations, claimable entry-point highlighting, and atomic batch planning (up to 50 issues, 100 relations, 20 decisions in one transaction). Review requests pin an exact issue version and event position — stale targets are superseded automatically.
One-command client setup. rhizome-mcp connect <target> generates and applies the MCP registration for claude, codex, vscode, or generic json — idempotent, with --print for a dry run.
Human observability without a server. rhizome-mcp board shows status counts, active leases with expiry, blockers, and the open review queue — as a terminal table, JSON, or a fully self-contained HTML snapshot (--output board.html) including the planning graph. Plus issue list, search, graph --format mermaid, doctor, and WAL-safe backup.
Portability. Pure-Go SQLite (modernc.org/sqlite, CGO-free), stdio as the primary transport, opt-in loopback-only HTTP with strict Host/Origin validation, and a versioned JSON interchange format for moving projects between installations.
Install
curl -fsSL https://raw.githubusercontent.com/Odrin/rhizome-mcp/main/scripts/install.sh | shirm https://raw.githubusercontent.com/Odrin/rhizome-mcp/main/scripts/install.ps1 | iexThe installers detect OS/architecture, verify the SHA-256 checksum, and install to ~/.local/bin by default. Manual downloads: pick the matching asset below (rhizome-mcp_<version>_<os>_<arch>.tar.gz, .zip on Windows) and verify it against the adjacent .sha256 file.
Then, inside your repository:
rhizome-mcp init
rhizome-mcp connect claude # or: codex | vscode | jsonSupported platforms: linux/amd64, linux/arm64, darwin/amd64, darwin/arm64, windows/amd64.
By-design constraints
Local single-developer tool: no web UI, no authentication, no multi-user permissions, no permanent agent identities, single-writer SQLite (not for multi-node deployment). Deferred features are documented in docs/06-deferred-and-open.md.
Documentation
- README — overview and quick start
- MCP tool catalog — the full 31-tool contract
- Specification index — nine modular spec documents
- CHANGELOG
Full Changelog: v1.0.0-beta.2...v1.0.0