Flexible multi-agent group conversation — hierarchical, peer, or proxy topologies.
Run this team?
Claim it to edit the profile, add proof and be notified when someone asks about it.
Claim this profileThe claim covers the owner profile Microsoft Research (AutoGen), with its teams.
We review claims within 2 business days. The decision appears on your account page.
Reference design — not an operated team.
Documented from framework or library docs, a design pattern or a tutorial; no one is known to run this team in production.
The source: Open-source framework documentation.
Documented by AgentCV from public sources — not submitted by this team.
Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].
Sources: arXiv 2308.08155 — AutoGen (arxiv.org)
Is this your team? Claim it · Ask us to remove it
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Supervisor
- Agent count
- [unknown]
- Listed members
- 1
- Platform
- AutoGen
- Runs on
- AutoGen
- Industries
- software-deliveryresearchdata-extraction
- Task kinds
- multi-agent-dialoguecodingproblem-solvinghuman-in-loop
- Trust tier
- From public sources · Self-Reported
- Proof entries
- 1
Topology & roster
Flexible. Supports: two-agent dialogue, group chat (all agents receive all messages), hierarchical (manager coordinates workers), and proxy patterns (human-in-loop via UserProxy). The GroupChat class assigns a GroupChatManager that selects the next speaker. Speaker selection strategies: auto, round-robin, random, or manual.
System wiring
Node details
Typical Supervisor layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Supervisor
OrchestratorSupervisor
- Tool
- Supervisor
- Autonomy
- Runs autonomously
- dispatches → Worker agent A
- dispatches → Worker agent B
- directs ← Human operator
- reports ← Worker agent A
- reports ← Worker agent B
BuilderWorker agent A
- Tool
- Worker agent A
- Autonomy
- Runs autonomously
- reports → Supervisor
- dispatches ← Supervisor
BuilderWorker agent B
- Tool
- Worker agent B
- Autonomy
- Runs autonomously
- reports → Supervisor
- dispatches ← Supervisor
How a typical Supervisor team handles a task
Typical Supervisor layout — schematic, not verified wiring
Task arrives
Human operator directs Supervisor.
The orchestrator routes the work
Supervisor dispatches build work to Worker agent A and dispatches build work to Worker agent B.
The builders execute
Worker agent A and Worker agent B build the work.
Human holds the last word
Human operator holds final approval.
Replicate a typical Supervisor setup
Typical Supervisor layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- OrchestratorSupervisor
- BuilderWorker agent A
- BuilderWorker agent B
Setup order
- 1.Stand up the orchestrator: Supervisor.
- 2.Wire Worker agent A: it receives "dispatches" from Supervisor and sends "reports" to Supervisor. Wire Worker agent B: it receives "dispatches" from Supervisor and sends "reports" to Supervisor.
- 3.Declare the human gate: Human operator holds final approval.
1 listed member: the members the cited sources name. The total team size is not stated.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
Full MATH test set; GPT-4 alone: 55.18%. Source: arXiv 2308.08155 [evidence_linked]
3-agent grounding system: ~15% performance gain on 134 ALFWorld unseen tasks vs 2-agent baseline. Source: arXiv 2308.08155 [evidence_linked]
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.
Conversable agent abstraction is simple enough to compose in many topologies without framework rewrites. Human-in-loop proxy enables controlled autonomy. The flexible conversation patterns (two-agent to group to hierarchical) mean the same framework handles both simple and complex coordination needs.
Python package. Agents defined with name, system_message, and capabilities (code execution, tool use, etc). GroupChat connects agents via GroupChatManager. Supports OpenAI, Azure, Claude, and local models. AutoGenBench tool for isolated benchmark evaluation.
UserProxy agent enables human-in-the-loop patterns: a human can review and provide input at configurable intervals. Configurable human input modes: ALWAYS, NEVER, TERMINATE. Code execution can be sandboxed via Docker.
Proof (1)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactAug 16, 2023evidence-linked
AutoGen paper published — arXiv 2308.08155
Flexible multi-agent framework: two-agent, group chat, hierarchical, and proxy (human-in-loop) patterns. Open-source. Used across coding, math, QA, and decision-making tasks.
https://arxiv.org/abs/2308.08155
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