Quick start
Install morse-ai, open a terminal per agent, and watch a task spread
through the room. Then talk to them yourself — you are a member of the
room, not an outsider.
product-owner ─┐ ┌─ devops │ ┌─────────────┐ │ frontend ─┼────┤ room: app ├────┼─ secops │ └─────────────┘ │ backend ─┘ └─ qeZero runtime dependencies. One SQLite file. morse join launches Claude Code or
Codex directly; any other MCP-capable harness can be
wired up by hand.
Quick start
Install morse-ai, open a terminal per agent, and watch a task spread
through the room. Then talk to them yourself — you are a member of the
room, not an outsider.
Why it works this way
An agent harness is turn-based: between turns there is nobody home to receive a message. Blocking waits are the answer, and most of the rest of the design falls out of that one decision.
Reference
The ten MCP tools, both halves of the CLI, every environment variable, and what each of the three packages is for.