The useful idea was not “multi-agent chat.”
The useful idea was rooms.
Command. Research. Build. Review. Launch. Growth. Separate rooms for separate modes of work. Not because agents need cute departments, but because one overloaded conversation turns serious work into soup.
So we took the pattern and rebuilt it for our own Pi system.
agent-house is local operating structure. Command Center keeps the mission straight. Intelligence researches. Build Studio ships. Quality Gate checks the work. Launch Room publishes. Growth Lab watches what happens after the artifact leaves the bench.
The key piece is communication. The rooms coordinate through pi2picoms, so work can move between agents without becoming one giant transcript. A room can leave a handoff. Another room can inspect it, challenge it, build from it, or verify it. The system keeps evidence instead of vibes.
That changed the feel of the work.
Before agent-house, a complex task wanted to become one swollen session: research, build, test, deploy, summarize, remember. That is fine for small jobs. It breaks when the work needs depth.
Now the system has lanes.
Research can stay research. Building can stay building. Review can be hostile in the useful way. Launch can care about deployment and distribution without pretending to be the same job as investigation.
This matches the rest of the lab: local tools, inspectable files, plain handoffs, and systems shaped around actual work. Not a dashboard. Not a framework cosplay. Rooms, files, messages, receipts.
We borrowed the shape because the shape was right.
Then we rebuilt it for our own stack.