VI · Multi-AgentEmerging★

Magentic-One Generalist Multi-Agent

also known as Magentic-One, Orchestrator + Specialist Agents (Microsoft)

Use Microsoft's generalist multi-agent architecture: a single Orchestrator agent dispatches to four specialist sub-agents (WebSurfer, FileSurfer, Coder, ComputerTerminal) for solving open-ended complex tasks that span web browsing, file manipulation, code execution and shell operations.

This pattern helps complete certain larger patterns —

  • specialisesOrchestrator-Workers★★— An orchestrator dynamically breaks a task into subtasks at runtime and delegates each to a worker LLM, then synthesises results.

Context

The team has an open-ended automation task: 'research X, write a report, run analysis, send it'. The task spans modalities — web, files, code, shell — none of which a single agent handles equally well. Building bespoke specialists per task is expensive.

Problem

Single-modality agents fail on cross-modality tasks. Bespoke multi-agent systems take significant engineering per task class. The team needs a generalist architecture that already covers the common modalities and orchestrates them sensibly.

Forces

  • Generalist architectures sacrifice depth in any one modality.
  • Orchestrator coordination is non-trivial.
  • Microsoft's specific specialist set may not match every team's needs.

Example

A team needs an automation agent for: 'pull the 2024 EU the agent Act revisions from the web, extract the diff against the 2023 version, run a frequency analysis on the changed terms, send the report'. Magentic-One: Orchestrator decomposes into 4 sub-tasks. WebSurfer pulls the EU site. FileSurfer manages the cached docs. Coder writes and runs the diff + frequency analysis. ComputerTerminal triggers the email send. Orchestrator integrates and reports. Task completes in one run.

Diagram

Solution

Therefore:

Deploy Magentic-One's five-component architecture. The Orchestrator decomposes user requests, plans, dispatches to specialists, integrates results. WebSurfer handles browser automation. FileSurfer navigates filesystems. Coder writes and runs code in isolated environments. ComputerTerminal executes shell commands. The Orchestrator maintains a task ledger and replan log. Pair with orchestrator-workers, supervisor, browser-agent, computer-use, one-tool-one-agent.

What this pattern forbids. The Orchestrator is the single coordination point; specialists do not directly dispatch to each other.

And the patterns that stand alongside it, or against it —

  • complementsSupervisor★★— Place a coordinating agent above a set of specialised agents and route work to them.
  • complementsBrowser Agent★— Expose websites to the agent through a structured DOM/accessibility tree plus a small action vocabulary, sitting between raw HTML and pixel-level Computer Use.
  • complementsComputer Use★— Let the model drive a desktop end-to-end via screenshots plus virtual mouse/keyboard tool calls instead of bespoke per-app APIs.
  • complementsOne Tool, One Agent★— Design agent systems as a team of narrow single-purpose agents, each owning one tool or one capability, rather than a single super-agent that handles every tool — the agent analogue of microservices over monolith.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance