waitbus
A workstation-local event bus: your AI coding agents wait on events instead of polling — and hear each other fail.
github ↗waitbus speaks, and a swarm waking from a single broadcast.- 01 Your AI coding agents can't hear each other — not even across vendors Your Claude Code, your Cursor, your tests, your CI — all on one box, none able to hear the others finish or fail. Here's the problem, and the proof: five real LLM agents on one bus, one fails, all wake.
- 02 How waitbus works: from event source to a waiting agent, over MCP The architecture end to end — how an event gets from a source to a waiting agent in single-digit milliseconds, how an agent actually talks to the bus over MCP, and the decisions behind the build with what each one cost.
- 03 The numbers and the trust trail: benchmarking waitbus honestly Two kinds of trust in one place — the benchmark methodology that makes the speed numbers survive a skeptic (Coordinated Omission, a bimodal p99, costs published as losses), and the supply-chain trail that lets you trust the artifact you install (SLSA provenance, sigstore, reproducible builds, and an honest list of the gaps).
- 04 The first file an agent reads Coding agents read your library before they use it, and they start with the code — `__init__.py`, the type hints, the tool schemas — not your docs site. Here is how I made waitbus speak to that reader, and the one piece of documentation I deliberately did not ship.