Triage-to-specialist handoff pattern — stateless, client-side, Chat Completions API.
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Orchestrator–Worker
- Agent count
- 3
- Platform
- OpenAI Swarm (deprecated)
- Runs on
- OpenAI Swarm (deprecated) ×2
- Industries
- customer-supportoperations
- Task kinds
- intent-routingcustomer-servicetask-handoff
- Trust tier
- Self-Reported
- Proof entries
- 1
Topology & roster
Hub-and-spoke (handoff-based). Triage agent acts as router; specialist agents handle domain-specific tasks. Handoffs are represented as tool calls that return a new Agent object. Specialists can hand back to triage or to other specialists. Each agent has its own instructions and tools.
System wiring
Node details
Typical Orchestrator–Worker layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Orchestrator
OrchestratorOrchestrator
- Tool
- Orchestrator
- Autonomy
- Runs autonomously
- dispatches → Worker agent
- requests gate → QA reviewer
- directs ← Human operator
BuilderWorker agent
- Tool
- Worker agent
- Autonomy
- Runs autonomously
- commits to → Shared workspace
- dispatches ← Orchestrator
QAQA reviewer
- Tool
- QA reviewer
- Autonomy
- Runs autonomously
- gate verdict → Shared workspace
- requests gate ← Orchestrator
ResourceShared workspace
- Tool
- Shared workspace
- Autonomy
- Runs autonomously
- commits to ← Worker agent
- gate verdict ← QA reviewer
How a typical Orchestrator–Worker team handles a task
Typical Orchestrator–Worker layout — schematic, not verified wiring
Task arrives
Human operator directs Orchestrator.
The orchestrator routes the work
Orchestrator dispatches build work to Worker agent.
Worker agent builds the work
Worker agent builds the work.
Independent review gates the work
QA reviewer reviews the work. This reviewer is autonomous and separate from the agent that built the work, so the check is independent of its author.
The artifact lands
The artifact lands in Shared workspace: Worker agent contributes via "commits to" and QA reviewer contributes via "gate verdict".
Human holds the last word
Human operator holds final approval.
Replicate a typical Orchestrator–Worker setup
Typical Orchestrator–Worker layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- OrchestratorOrchestrator
- BuilderWorker agent
- QAQA reviewer
- ResourceShared workspace
Setup order
- 1.Provision the substrate: Shared workspace.
- 2.Stand up the orchestrator: Orchestrator.
- 3.Wire Worker agent: it receives "dispatches" from Orchestrator. Wire QA reviewer: it receives "requests gate" from Orchestrator.
- 4.Give QA reviewer an independent workspace/verdict channel: "gate verdict" to Shared workspace.
- 5.Declare the human gate: Human operator holds final approval.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
OpenAI Swarm is an educational/experimental framework; no benchmark figures in repository. Source: github.com/openai/swarm
Token economics
Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.
Blueprint
Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.
Handoff primitive is simple and composable: any agent can route to any other via a tool call. Stateless design eliminates server-side coordination infrastructure. The educational focus means the code is minimal and readable, making it useful as a reference pattern even in its deprecated state.
Python package built on top of Chat Completions API. Agents defined with instructions and tools (Python functions). Handoffs are tool functions returning another Agent. The run_demo_loop() utility handles the REPL. Examples in the repo: triage agent, airline customer service, weather agent, and others.
Stateless design: all state is in the messages array, making the full conversation history inspectable. Designed as an educational framework — the source recommends the OpenAI Agents SDK for production use. Source: Swarm GitHub.
Proof (1)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactOct 11, 2024evidence-linked
OpenAI Swarm GitHub repository published (educational, now deprecated)
Core primitive: handoff — an agent transfers conversation control to another agent. Stateless: all state in the messages array. Superseded by OpenAI Agents SDK for production use.
https://github.com/openai/swarm
Sign in to add a proof entry.
Sign inAttestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this team.
Sign in