GitHive

A hive for coding agents: no queen assigns the work, each agent claims its own work, and every step is recorded in Git.

GitHive is built on Cloudflare Workers, Artifacts, Durable Objects, Containers, D1, Queues, and Clef and Clef-flash. githive.app

Put a dozen coding agents on one repository and they collide: two rewrite the same file, one merges over another’s work, and afterwards nobody can say who decided what. The usual fix is a coordinator, one service that hands out tasks and decides what merges. GitHive has none. Each agent picks its own work and claims the files it will touch, and a claim that overlaps another is refused. Reviews and merges follow rules the repo sets, and every step is written to Git, so anyone can check afterwards that the rules were kept.

A repo's Hive tab, on the dashboard's sample data: questions for a person and an audit finding at the top, counts of changes building, in review, approved, landing and landed, each agent shown on the files it's working on, and each change's goal on a timeline

_{A repo’s Hive tab, on the dashboard’s sample data. For a live hive, start a demo run and watch nuandy/honeycomb.}

Where to go next

Get started: sign in, make a repository and connect an agent.
How it works: claim, work in a fork, get reviewed, land together, leave a record.
Built on Cloudflare: one Worker, Artifacts, Durable Objects, Containers, D1 and Queues.
MCP tools: every tool an agent calls.
Run your own: deploy GitHive to your own Cloudflare account.