open-multi-agent/examples

Examples

Runnable scripts demonstrating open-multi-agent. Organized by category — pick one that matches what you're trying to do.

All scripts run with npx tsx examples/<category>/<name>.ts and require the corresponding API key in your environment.

---

basics — start here

The four core execution modes. Read these first.

Example	What it shows
basics/single-agent	One agent with bash + file tools, then streaming via the Agent class.
basics/team-collaboration	runTeam() coordinator pattern — goal in, results out.
basics/task-pipeline	runTasks() with explicit task DAG and dependencies.
basics/multi-model-team	Different models per agent in one team.

providers — model & adapter examples

One example per supported provider. All follow the same three-agent (architect / developer / reviewer) shape so they're easy to compare.

Example	Provider	Env var
providers/ollama	Ollama (local) + Claude	ANTHROPIC_API_KEY
providers/gemma4-local	Gemma 4 via Ollama (100% local)	—
providers/copilot	GitHub Copilot (GPT-4o + Claude)	GITHUB_TOKEN
providers/grok	xAI Grok	XAI_API_KEY
providers/gemini	Google Gemini	GEMINI_API_KEY
providers/minimax	MiniMax M2.7	MINIMAX_API_KEY
providers/deepseek	DeepSeek Chat	DEEPSEEK_API_KEY
providers/groq	Groq (OpenAI-compatible)	GROQ_API_KEY

patterns — orchestration patterns

Reusable shapes for common multi-agent problems.

Example	Pattern
patterns/fan-out-aggregate	MapReduce-style fan-out via AgentPool.runParallel().
patterns/structured-output	Zod-validated JSON output from an agent.
patterns/task-retry	Per-task retry with exponential backoff.
patterns/multi-perspective-code-review	Multiple reviewer agents in parallel, then synthesis.
patterns/research-aggregation	Multi-source research collated by a synthesis agent.
patterns/agent-handoff	Synchronous sub-agent delegation via delegate_to_agent.

integrations — external systems

Hooking the framework up to outside-the-box tooling.

Example	Integrates with
integrations/trace-observability	onTrace spans for LLM calls, tools, and tasks.
integrations/mcp-github	An MCP server's tools exposed to an agent via connectMCPTools().
integrations/with-vercel-ai-sdk/	Next.js app — OMA runTeam() + AI SDK useChat streaming.

production — real-world use cases

End-to-end examples wired to real workflows. Higher bar than the categories above. See production/README.md for the acceptance criteria and how to contribute.

---

Adding a new example

You're adding…	Goes in…	Filename
A new model provider	providers/	<provider-name>.ts (lowercase, hyphenated)
A reusable orchestration pattern	patterns/	<pattern-name>.ts
Integration with an outside system (MCP server, observability backend, framework, app)	integrations/	<system>.ts or <system>/ for multi-file
A real-world end-to-end use case	production/	<use-case>/ directory with its own README

Conventions:

• No numeric prefixes. Folders signal category; reading order is set by this README.
• File header docstring with one-line title, Run: block, and prerequisites.
• Imports should resolve as from '../../src/index.js' (one level deeper than the old flat layout).
• Match the provider template when adding a provider: three-agent team (architect / developer / reviewer) building a small REST API. Keeps comparisons honest.
• Add a row to the table in this file for the corresponding category.