A room is a directory with three files. That is the whole pattern.
What is a room?
Agent-house is a multi-agent workflow system that runs inside Pi using Pi Coms for agent-to-agent messaging. A room is a self-contained team of agents with a specific purpose: research, build, review, or launch.
Seven rooms exist today — intelligence, build-studio, quality-gate, launch-room, product-design, command-center, and growth-lab. Each has its own orchestrator, workers, and verifier. Each can run independently. Each leaves a handoff for the next room.
The three files
Every room needs exactly three files:
1. ROOM.json — defines the team roster. Each agent entry specifies name, role (lead, worker, verifier), model, tools, and optional extensions or fallback models. Different agents can use different models within the same room.
2. TEAM.md — describes the room's purpose, when to enter it, the room contract, agent responsibilities, safety gates, and standard output format. The orchestrator reads this to understand its job.
3. enter — a one-line shell script that calls the agent-house CLI with the room name.
How routing works
The agent-house CLI has a keyword-based router. When you send a task, it scans each room's keyword list and routes to the best match. Research keywords go to intelligence. Build keywords go to build-studio. Review keywords go to quality-gate.
How a room run works
agent-house enter <room> --task "..."starts tmux sessions for each worker- Workers register on Pi Coms
- The orchestrator session opens in the foreground
- It delegates tasks via coms, workers execute independently
- Results are saved to a timestamped folder under the room's results directory
- The room outputs a HANDOFF.md with next-room recommendation
Handoff is currently manual — you copy the next room command from the handoff and run it yourself. This will become automatic.
Creating a new room
- Create a directory for the new room
- Write ROOM.json with your agents
- Write TEAM.md with the brief
- Write the enter script
- Add a route entry in the agent-house router's keyword list
- Register it in the agent-house manifest
That is it. No Docker. No API gateway. No queue. A JSON file, a Markdown file, and a shell script.