Beadhive · Field Guide

Agentic Git Flow, driven by beads

How the Beadhive factory turns raw ideas into an always-green integration branch — with agents doing the work, humans holding the gates, and a dependency-linked issue tracker (beads) as the shared memory that makes both possible.

AGF — Agentic Git FlowThe abstract, tracker-independent process: operational planes, seats, worktree-per-bead, review gates, serialized merges.
BeadflowAGF implemented on beads — the concrete process this repo runs. Same behavior, bead-backed.
Beadhive · bhThe umbrella brand and its CLI: the integration-plane driver that encodes the conventions, registry, validation, and routing.
Install · two commands

bh is a Python CLI. It drives bd (beads) for issues andgit for history — there is no server to run and nothing to sign up for.

uv tool install 'beadhive[otel]'
bh config init

That leaves you a working bh and a config home at ~/.beadhive/. Point it at a repo with bh hive onboard, then ask what's actionable withbh work ready.

Using Claude Code? Add the plugin

Recommended, not required. The plugin vends the seat agent definitions and role skills — planner, dispatcher, developer, reviewer, merger and the rest — so an agent can take a seat directly instead of improvising the lifecycle. The last line wires the MCP server.

claude plugin marketplace add beadhive/claude-plugin
claude plugin install bh@beadhive
bh mcp install

Full setup, from a fresh machine to a configured workspace with registered hives:INSTALL.md ·docs/ONBOARDING.md

The field guide · four chapters