/pattern/magentic/

03 · Multi-AgentMagentic-One Style OrchestrationGeneralist Multi-Agent Team

Magentic.
Plan. Delegate. Synthesize. Over long horizons.

An orchestra of specialized agents combines planning, a task ledger, delegation, and replanning for long-running, complex goals.

When to reach for it

  • Tasks are open-ended, multi-step, and tool-intensive.
  • Multiple specialists must operate with high autonomy over long horizons.

When it backfires

  • A simple workflow suffices.
  • Auditability requires deterministic steps.
  • Operating costs are strictly limited.

The tradeoff

Massive task coverage is gained against exceptionally high operational and orchestration complexity.

The mental model

A shape you can draw on a napkin.

A planner-supervisor maintains a task ledger, delegates to specialists, and synthesizes results across long-running goals.

PlannerSpecialist ASpecialist BSpecialist C
Pitfalls

Two ways this pattern will hurt you.

Task ledger grows faster than it completes

The planner keeps adding subtasks without closing existing ones. The ledger becomes an infinite to-do list.

Fix · Require every delegation to include a completion criterion. Close ledger entries explicitly, not by timeout.

Replanning discards specialist context

A mid-flight replan reassigns a task to a different specialist, but the new specialist lacks the context the first one built.

Fix · Persist intermediate state with each ledger entry. Hand off both the task and the accumulated context.

Framework support

Where Magentic is native.

Microsoft Agent Frameworkproduction successor to the Magentic-One research prototypeNative
AutoGen / AG2community implementationsAdaptable
LangGraphas custom graphAdaptable

Search

Search patterns, frameworks, and pages.