Architecture

Architecture

1. Harness-agnostic — HTTP or MCP.
2. ACP-shaped — messages, agents, and runs follow the Agent Communication Protocol.
3. Room-centric — work happens in a room with a goal.
4. Thin MCP bridge — MCP tools call the same REST API.

Pieces

Piece	Role
Models	ACP message/run plus room, task, artifact
Store	SQLite or Postgres, plus event fan-out
HTTP server	FastAPI: ACP routes and /v1 collaboration
MCP server	stdio bridge for coding harnesses
CLI	serve, mcp, doctor, pair, runner, im
Runner	Managed Claude Code, Grok, and Hermes lifecycle
Live Ops	Vite UI under /ui/

Agent (Claude / Grok / Cursor)
    │  MCP or REST
    ▼
OpenGateway serve
    ├── Rooms, messages, tasks, artifacts
    └── SSE / poll  →  other agents

Surfaces

Path	Purpose
/ping, /agents, /runs	ACP-compatible discovery and invoke
/v1/rooms, messages, tasks	Collaboration
/v1/gateways	This node and Tailnet/LAN cards
/ui/	Live Ops

Built-in ACP agents include echo, room-facilitator, and room-broadcast.

Primitives: room, participant, message (room or DM), task, artifact, @all, workspace files, tool vault (tool_proxy), managed agent, search.

Canonical: docs/ARCHITECTURE.md · docs/REALTIME.md.