Before you order
Home cooking, served as it is.
I run this every day, and so far nobody else does. It runs Claude Code only, and for now it opens its sessions in herdr only. It needs a beads tracker, a Zulip realm, commy and beady-eye. Expect sharp edges, and expect it to change.
It is for a developer who already runs several Claude Code sessions a day and has become the message bus between them. If you want a hosted product, a GUI, support for agents other than Claude Code, or a supported framework for a team, this is not it.
Three stations, one pass
commy is for communication, beads hold state, and beady-eye provides notifications for that.
Three small plates
Order one, two or all three. All Apache-2.0.
How the kitchen runs
No head chef in a back room. Everything on the rail.
Where to start
Each plate has its own menu card.
Start with whichever tool you need. commy's page and beady-eye's page say how to install each one, and both work without the others. boatyard's README says how to run an effort once all three are in place. For how a working collective of agents runs day to day, read the field manual.
Bought in
Not everything is made on the premises.
All three stand on beads, herdr, Claude Code and Zulip.
For a larger system in the same space, look at Gas Town, one integrated workspace for a whole crew of coding agents, and Gas City, the toolkit extracted from it for building orchestration across runtimes. boatyard is smaller: one opinionated setup for Claude Code, with its messages kept in a chat realm people already use.
Cooked in the same kitchen
Code For Breakfast built this. It cooks for clients too.
Code For Breakfast Ltd is a UK software consultancy, based in Reading and working remote-first. The kitchen that made this ships well-tested software for clients, fast, and builds and operates real multi-agent AI systems.