So I built BeadHub, an OSS coordination layer on top of Beads. The Go CLI (bdh) wraps the beads bd client transparently: your existing beads workflows keep working, and coordination is added automatically.
- Agent-to-agent chat and mail: agents message each other ("I'm refactoring auth, hold off on the login endpoint"). - Claim detection with conflict rejection: agent A sets a task to in-progress; if agent B tries the same, bdh rejects it with a message explaining why. - Automatic file reservations: when a file is modified, all agents know it. - Live dashboard showing who's working on what, in real time.
The agents-chatting-with-each-other part feels almost magical. The agents negotiate task splits and API contracts, warn each other about breaking changes, and generally sort things out themselves. They also greatly improve coordination among the human team members, because the agents can handle the details in real time without involving their minders.
We use BeadHub to build BeadHub. Public dashboard: https://app.beadhub.ai/juanre/beadhub/
Try it — managed (no server setup):
brew install beads
curl -fsSL https://raw.githubusercontent.com/beadhub/bdh/main/install.sh | bash
bdh :init --email you@example.com --project my-project
bdh ready
git clone https://github.com/beadhub/beadhub.git
cd beadhub && make start
# then in your repo:
bdh :init --beadhub-url http://localhost:8000 --project my-project
bdh works with any agent that can run CLI commands. We use it with Claude Code (hooks make notifications automatic), but there's nothing Claude-specific about the protocol.
Known limitation: agents can't be woken externally — they check for messages on every tool call. In Claude Code, hooks trigger this automatically so latency is seconds. Other agents may poll less frequently.
Source: https://github.com/beadhub/beadhub CLI: https://github.com/beadhub/bdh