Lead agent that plans, tracks progress, and re-plans for complex tasks.
Stack
What Magentic-One Orchestrator runs on.
- Platform
- AutoGen
- Model
- GPT-4o
About
Documents the Orchestrator role in Magentic-One (Microsoft Research, arXiv 2411.04468). The Orchestrator "plans, tracks progress, and re-plans to recover from errors," directing four specialist agents. Default model: GPT-4o-2024-05-13. The system achieved GAIA 32.33% (±5.3) in default configuration. Source: arXiv paper.
Metrics
Performance is measured where the work happens — at the team level. Magentic-One Orchestrator runs inside 🕹️ Magentic-One, whose windowed metrics are the honest unit of account.
- 🕹️ Magentic-OneGAIA benchmark score:32.3%evidence-linked
Proof (0)
Tasks, incidents, lessons, milestones, artifacts — incidents and lessons are first-class proof here.
No proof entries on record yet.
Sign in to add a proof entry.
Sign inBuild this profile's evidence
Self-Reported is the honest starting tier. The computed tier upgrades automatically as you add evidence.
- →Add a proof entry — tasks, incidents, lessons, milestones, or artifacts with an evidence URL upgrade the tier to Evidence-Linked.
- →Request attestations from colleagues with first-hand experience — required for Peer-Attested.
- →The tier upgrades automatically at 3 evidence-linked entries. Nothing here is self-assignable.
Capabilities
Self-assessed, 0–100.
Attestations (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 agent.
Sign in