// how it works

How OMA works.

Two diagrams, one system. The architecture is the structure — what OMA is. The flow is time — what happens when you call runTeam(). Same visual language, translated from the brand system.

01 structure

The architecture.

Five layers, top to bottom: the orchestrator you call, the team it coordinates, the pool and queue that schedule the work, the agent that does it, and the adapter, runner, and tool interfaces underneath. Every box maps one-to-one to a type in the framework.

OMA architecture. OpenMultiAgent is the entry point and owns a Team, which holds an AgentPool and a TaskQueue. The Agent runs through an AgentRunner conversation loop and talks to the LLMAdapter interface (multiple provider implementations) and the ToolRegistry (defineTool plus 6 built-in tools).
  • accent borderUser entry point — the class you instantiate. Exactly one per diagram.
  • solidConcrete type — a class with one implementation: Team, AgentPool, TaskQueue, Agent, AgentRunner.
  • dashedInterface with multiple implementations — LLMAdapter providers, ToolRegistry tools.
  • arrowOwns / contains — the source instantiates or owns the target. Read top-down.
02 execution

One runTeam() call.

Goal in, result out. The coordinator decomposes the goal into a task DAG, fans the agents out in parallel, carries intermediate results over the MessageBus, and synthesizes the final answer. Read it left to right — the horizontal axis is time.

The runTeam() flow. A goal decomposes into four tasks; an architect and two developers run in parallel, the reviewer waits on them via a TaskQueue dependency, the MessageBus connects the tracks, and a typed result object is synthesized at the end.
  • vertical = which agentEach agent gets its own horizontal track, like a voice in a music score.
  • horizontal = whenTracks aligned at the same x run at the same logical time; a track that ends earlier finished first.
  • reviewer waitsThe reviewer is offset right — a TaskQueue dependency on the architect and the two developers.
  • message busThe dashed-emerald band is the channel any agent can publish to and subscribe from during execution.
// go deeper

From diagram to code.

runAgent · runTeam · runTasks→ Quick Start→