1.0: done, not big
Most 1.0 announcements promise that things are about to get bigger. Ours promises the opposite: the wire will not break under you. agentchute 1.0 is out.
Blog
Writing on protocol design, multi-agent coordination, and the practice of letting the agents that build the protocol use it to coordinate the build.
-
-
After 1.0: the roadmap around a stable core
Protocol v2 is stable, so the roadmap is everything around it: self-serve conformance certification, a cleaner cue channel, git-backed pools, and hub-and-spoke.
-
0.8.0: agentchute, simple again
We built a liveness/wake subsystem to make sender-side 'poke the recipient' reliable — then deleted it. 0.8 is pull-only: senders write to an inbox and walk away, recipients read on their own cadence. The trim is the release.
-
v0.3.5: tmux teams, worktrees, and contextual identity
The tmux reference path now handles worktrees and same-folder agents with contextual IDs, safer enrollment refreshes, and hook templates that no longer hardcode identities.
-
The agents debugged their own message bus
A fourteen-agent fleet exposed an identity bug in agentchute itself: same-vendor lanes all sharing one inbox, the finish-gate waved through. Four agents diagnosed it, fixed it, and ran a four-way verification loop — over the bus they were repairing.
-
v0.3.2: one-line setup and transparent coordination
Install + repo wiring collapses into a single command. Launcher shims route claude/codex/gemini through the runner so the wrapper commands you already use start coordinating. Wake events become visibly machine-typed.
-
v0.2: recipient polling, by hand and by hook
tmux made the first agentchute demos feel immediate. It also blurred the protocol boundary. v0.2 fixes that — self-poll and doctor --generate-service (both removed in v0.9.0), gate --before continue, and a §8.2 spec clarification that recipient polling is canonical.
-
You are the message bus
How we stopped copy-pasting between four AI agent terminals — and accidentally shipped a coordination protocol along the way.
Archive
- v0.2.1: enrollment, enforced · May 20, 2026 · Historical — operational deep-dive on the v0.2.1 enforcement gap.
- v0.1.2: doctor, watch, and the no-tmux path · May 20, 2026 · Historical — superseded by v0.2 recipient polling.
- v0.1.1: the agents shipped it themselves · May 20, 2026 · Historical — three agents shipping v0.1.1 using v0.1.0.