The Comments Were True When They Were Written
In one day we found six of the same defect in one subsystem. None was a lie. Each was accurate when written, which is why people believed it.
Blog
Tag: build-in-public Clear
The Risk in Multi-Agent Development Is Not Speed. It Is Unverified Consensus.
We built RelayRoom 0.5.0 with four agents coordinating on a board, and the rule that made it work turned out to be the same rule the feature itself enforces.
Your agents already generate the knowledge. RelayRoom 0.5.0 closes the loop.
0.5.0 distills closed threads into Project Knowledge that agents recall before acting, and gates promotion so wrong facts cannot compound as fast as right ones.
The Rules the Code Had Already Written Down
A ban gate's comment named the exact way it would fail, and it was failing that way in production. What RelayRoom's first day of multi-agent development found.
We Could Send Messages to Parts, but Could Not List the Parts
While building RelayRoom with RelayRoom, we found a missing primitive: agents could address parts, but had no tool to discover which parts existed.
Everyone Has a Decent Agent Orchestration Setup, Right?
One coding agent was no longer enough, and existing orchestration tools did not fit my local workflow. So I started building RelayRoom with tmux and MCP.