an open-source alternative to the dots, bots and muses of the world, run an office of claude code/codex like agents on your laptop, sandboxes or anywhere, uses your existing subscriptions
HTML agent-harnessagent-orchestrationagentsai-agentsautonomous-agentsclaude-codecodexcoding-agentsdesktop-appdeveloper-toolselectrongemini-cliharnessharness-engineeringlocal-firstmemorymulti-agentopencodeorchestrationtypescript
<!doctype html>
<html lang="en">
<head>
<!-- Google tag (gtag.js), Google Ads AW-18388216863. Loaded only when Do Not Track is
off, so it follows the same rule as the PostHog block on this site. -->
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){ dataLayer.push(arguments); }
if (navigator.doNotTrack !== '1') {
var gtagScript = document.createElement('script');
gtagScript.async = true;
gtagScript.src = 'https://www.googletagmanager.com/gtag/js?id=AW-18388216863';
document.head.appendChild(gtagScript);
gtag('js', new Date());
gtag('config', 'AW-18388216863');
}
</script>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Multi-Agent Orchestration Patterns: Which Topology, and When — Munder Difflin Blog</title>
<meta name="description" content="The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins." />
<link rel="canonical" href="https://munderdiffl.in/blog/multi-agent-orchestration-patterns/" />
<link rel="icon" type="image/png" href="https://munderdiffl.in/logo.png" />
<link rel="apple-touch-icon" href="https://munderdiffl.in/logo.png" />
<meta name="theme-color" content="#F5F2E8" />
<!-- Open Graph -->
<meta property="og:site_name" content="Munder Difflin Blog" />
<meta property="og:type" content="article" />
<meta property="og:title" content="Multi-Agent Orchestration Patterns: Which Topology, and When — Munder Difflin Blog" />
<meta property="og:description" content="The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins." />
<meta property="og:url" content="https://munderdiffl.in/blog/multi-agent-orchestration-patterns/" />
<meta property="og:image" content="https://munderdiffl.in/blog/assets/media/multi-agent-orchestration-patterns/hero.png" />
<meta property="og:image:width" content="1600" />
<meta property="og:image:height" content="900" />
<meta property="og:image:alt" content="Illustration: Multi-Agent Orchestration Patterns: Which Topology, and When" />
<meta property="og:locale" content="en_US" />
<meta property="article:published_time" content="2026-06-05T00:00:00.000Z" />
<meta property="article:author" content="Chaitanya Giri" />
<meta property="article:tag" content="Orchestration" />
<meta property="article:tag" content="Multi-Agent" />
<meta property="article:tag" content="Concepts" />
<meta property="article:tag" content="Architecture" />
<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Multi-Agent Orchestration Patterns: Which Topology, and When — Munder Difflin Blog" />
<meta name="twitter:description" content="The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins." />
<meta name="twitter:image" content="https://munderdiffl.in/blog/assets/media/multi-agent-orchestration-patterns/hero.png" />
<meta name="twitter:image:alt" content="Illustration: Multi-Agent Orchestration Patterns: Which Topology, and When" />
<link rel="alternate" type="application/atom+xml" title="Munder Difflin Blog" href="https://munderdiffl.in/blog/feed.xml" />
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,[email protected],500;9..144,600;9..144,700;9..144,900&family=Source+Serif+4:opsz,[email protected],400;8..60,600;8..60,700&family=Space+Grotesk:wght@500;600;700&family=JetBrains+Mono:wght@400;600&display=swap" rel="stylesheet" />
<link rel="stylesheet" href="/blog/assets/blog-press.css" />
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Multi-Agent Orchestration Patterns: Which Topology, and When",
"description": "The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins.",
"image": ["https://munderdiffl.in/blog/assets/media/multi-agent-orchestration-patterns/hero.png"],
"datePublished": "2026-06-05T00:00:00.000Z",
"dateModified": "2026-06-05T00:00:00.000Z",
"author": { "@type": "Person", "name": "Chaitanya Giri" },
"publisher": {
"@type": "Organization",
"name": "Munder Difflin",
"logo": { "@type": "ImageObject", "url": "https://munderdiffl.in/logo.png" }
},
"mainEntityOfPage": { "@type": "WebPage", "@id": "https://munderdiffl.in/blog/multi-agent-orchestration-patterns/" },
"keywords": "multi-agent orchestration patterns, agent orchestration topologies, orchestrator worker pattern, supervisor agent pattern, when to use multi-agent",
"articleSection": "Orchestration",
"inLanguage": "en-US",
"url": "https://munderdiffl.in/blog/multi-agent-orchestration-patterns/"
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://munderdiffl.in/" },
{ "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://munderdiffl.in/blog/" },
{ "@type": "ListItem", "position": 3, "name": "Multi-Agent Orchestration Patterns: Which Topology, and When", "item": "https://munderdiffl.in/blog/multi-agent-orchestration-patterns/" }
]
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{ "@type": "Question", "name": "What are the main multi-agent orchestration patterns?", "acceptedAnswer": { "@type": "Answer", "text": "Six recur: orchestrator-worker (a.k.a. supervisor — a central agent decomposes and delegates), hierarchical (supervisors of supervisors), sequential pipeline (fixed linear stages), parallel fan-out (scatter-gather over independent tasks), debate/maker-checker (one agent produces, another verifies), and blackboard (agents coordinate through shared state). Most production systems lean on orchestrator-worker." } },
{ "@type": "Question", "name": "Which orchestration pattern should I use?", "acceptedAnswer": { "@type": "Answer", "text": "Match it to your dependency structure: linear dependencies → pipeline; independent tasks → fan-out; accuracy-critical work → maker-checker; known sub-tasks with one accountable owner → orchestrator-worker (the 2026 default). Start with the simplest pattern that fits — most teams over-architect and add agents they don't need." } },
{ "@type": "Question", "name": "Is a multi-agent system always better than a single agent?", "acceptedAnswer": { "@type": "Answer", "text": "No. In benchmarks, a single agent matched or beat multi-agent systems on a majority of tasks when given the same tools and context, and a large share of multi-agent pilots fail in production — usually from the wrong pattern. More agents add coordination cost; they pay off only when the task genuinely decomposes." } }
]
}
</script>
<script>
// Anonymous blog analytics (PostHog) — same posture as the main site and the
// app's TELEMETRY.md: public write-only token ('' = inert), anonymous-only
// (person_profiles 'never'), no autocapture/recording, DNT respected.
(function () {
var PH_KEY = 'phc_qJzsokwcbtTGHemnvywR3nSqivNNgMjHeNVEWkZNydFB';
if (!PH_KEY || navigator.doNotTrack === '1') return;
var s = document.createElement('script');
s.async = true;
s.src = 'https://us-assets.i.posthog.com/static/array.js';
s.onload = function () {
if (!window.posthog) return;
window.posthog.init(PH_KEY, {
api_host: 'https://us.i.posthog.com',
person_profiles: 'never',
autocapture: false,
before_send: function (event) {
// PostHog fills $ip from the connection unless the event carries one.
// Null it here and disable the GeoIP lookup so no IP, city, postal
// code or lat/long is ever derived or stored for this page view.
if (event && event.properties) {
event.properties.$ip = null;
event.properties.$geoip_disable = true;
}
return event;
},
disable_session_recording: true,
respect_dnt: true
});
};
document.head.appendChild(s);
})();
</script>
</head>
<body class="theme-press">
<a class="skip-link" href="#main">Skip to content</a>
<nav id="nav">
<a class="brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
<img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
</a>
<span class="spacer"></span>
<div class="links">
<a href="/blog/">Latest</a>
<a href="/blog/topics/">Topics</a>
<a href="/blog/about/">About</a>
<a href="https://munderdiffl.in">↗ Product</a>
</div>
<div class="nav-actions">
<a class="btn sm" href="https://munderdiffl.in/blog/feed.xml" aria-label="RSS feed">⤵ RSS</a>
<a class="btn sm primary" href="https://munderdiffl.in/#install">⤓ Download</a>
</div>
</nav>
<main id="main">
<article class="t-orchestration">
<header class="post-head wrap">
<nav class="crumbs" aria-label="Breadcrumb">
<a href="/blog/">Blog</a>
<span>/</span>
<a href="/blog/topics/orchestration/">Orchestration</a>
</nav>
<h1>Multi-Agent Orchestration Patterns: Which Topology, and When</h1>
<p class="dek">The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins.</p>
<div class="byline">
<span class="av" aria-hidden="true">CG</span>
<strong>Chaitanya Giri</strong>
<span class="dot" aria-hidden="true">·</span>
<time datetime="2026-06-05">Jun 5, 2026</time>
<span class="dot" aria-hidden="true">·</span>
<span>5 min read</span>
<span class="tag kind">Orchestration</span>
</div>
</header>
<div class="hero-wrap wrap"><figure class="fig fig-hero"><img src="/blog/assets/media/multi-agent-orchestration-patterns/hero.png" alt="Illustration: Multi-Agent Orchestration Patterns: Which Topology, and When" loading="lazy" decoding="async" /></figure></div>
<div class="post-wrap wrap">
<div class="prose">
<div class="callout tldr"><span class="ic">TL;DR</span><p>Multi-agent systems come in a few named
<strong>topologies</strong> — orchestrator-worker (supervisor), pipeline, fan-out, debate/maker-checker,
swarm, and blackboard. <strong>Orchestrator-worker is the 2026 default.</strong> But the most important
fact is the anti-hype one: a <strong>single agent often matches or beats</strong> a multi-agent system on
the same task, and many multi-agent pilots fail — usually from picking the wrong pattern. Rule: start with
the simplest topology that fits, add agents only when the problem genuinely decomposes, and make whatever
you pick <strong>survivable</strong>.</p></div>
<p>Once you’ve decided you need more than one agent, the next question is <em>how they’re wired together</em> —
the topology. There’s a small, well-worn set of patterns, each suited to a different shape of problem.
This is the catalog, when to reach for each, the honest caveats, and how the patterns show up in a real
<a href="/#how">multi-agent hive</a>.</p>
<h2 id="the-pattern-catalog" tabindex="-1">The pattern catalog <a class="anchor" href="#the-pattern-catalog" aria-hidden="true">#</a></h2>
<ul>
<li><strong>Orchestrator-worker (supervisor).</strong> A central orchestrator classifies the task, decomposes it,
dispatches sub-tasks to specialized workers, and merges the results. One clear accountability point, and
workers can run cheaper task-specific models — say, a research orchestrator that dispatches lookups to
small, fast workers and reserves a strong model for the final synthesis. <strong>Use when</strong> you know the
sub-tasks at design time and want one place that owns the outcome. This is the 2026 production workhorse.</li>
<li><strong>Hierarchical (supervisors of supervisors).</strong> Tiered orchestrator-worker: higher tiers plan and
coordinate, lower tiers execute. <strong>Use when</strong> the work is too big for one orchestrator’s context — teams
of teams.</li>
<li><strong>Sequential pipeline.</strong> Fixed linear stages, each consuming the previous output. <strong>Use when</strong> the order
never changes and steps strictly depend on each other (extract → transform → validate).</li>
<li><strong>Parallel fan-out (scatter-gather).</strong> Dispatch N independent sub-tasks at once, then gather. <strong>Use
when</strong> you have several tasks with no dependencies between them — the classic latency win.</li>
<li><strong>Debate / maker-checker.</strong> One agent produces, another critiques or verifies; iterate or vote. <strong>Use
when</strong> accuracy matters more than speed — review loops, adversarial checks.</li>
<li><strong>Swarm / network (peer).</strong> Dynamic peer agents hand off to each other with no central conductor. <strong>Use
when</strong> the path is emergent and data-dependent — and budget for it being the hardest to debug and bound.</li>
<li><strong>Blackboard.</strong> Agents read and write a shared workspace rather than messaging directly; the shared
state coordinates them. <strong>Use when</strong> many agents contribute to one evolving artifact.</li>
</ul>
<h2 id="a-decision-framework" tabindex="-1">A decision framework <a class="anchor" href="#a-decision-framework" aria-hidden="true">#</a></h2>
<p>You can get most of the way with three rules:</p>
<ol>
<li><strong>Default to supervisor / orchestrator-worker.</strong> It’s legible, accountable, and debuggable — which is
why it dominates production.</li>
<li><strong>Match the topology to the dependency structure.</strong> Linear deps → pipeline. No deps → fan-out.
Accuracy-critical → maker-checker. Emergent path → swarm (with guardrails).</li>
<li><strong>Start simple.</strong> Most teams over-architect. Reach for more agents only when a single agent genuinely
can’t hold the task.</li>
</ol>
<figure class="fig fig-inline"><img src="/blog/assets/media/multi-agent-orchestration-patterns/note-1.png" alt="Hand-drawn sketch from “Multi-Agent Orchestration Patterns: Which Topology, and When”" loading="lazy" decoding="async" /></figure>
<h2 id="patterns-compose" tabindex="-1">Patterns compose <a class="anchor" href="#patterns-compose" aria-hidden="true">#</a></h2>
<p>Real systems rarely use one pattern in isolation — they nest. A supervisor’s workers might each run a
maker-checker loop internally; a sequential pipeline might fan out within a single stage; a hierarchical
team might keep a blackboard at each tier to pool findings. The patterns are a <em>vocabulary</em>, not a menu you
pick one item from. The discipline is the same at every level of nesting: at each composition point, ask
what the dependency structure of <em>that</em> sub-problem is, and choose the topology that fits it.</p>
<p>A common, effective shape is a <strong>supervisor on the outside</strong> — one accountable owner with clear
decomposition — wrapping <strong>fan-out and maker-checker on the inside</strong>: run the independent sub-tasks in
parallel, and route the risky or accuracy-critical ones through a verifier. Compose deliberately, though:
every boundary you add is another place coordination can fail, and another handoff to debug.</p>
<h2 id="the-honest-part-multi-agent-isnt-free" tabindex="-1">The honest part: multi-agent isn’t free <a class="anchor" href="#the-honest-part-multi-agent-isnt-free" aria-hidden="true">#</a></h2>
<p>Two findings are worth leading with, so this stays grounded and not hype:</p>
<ul>
<li><strong>A single agent often wins.</strong> In benchmarking, a single agent matched or outperformed multi-agent
systems on a majority of tasks when given the same tools and context. More agents add coordination
overhead, latency, and cost — the payoff only appears when the task truly decomposes.</li>
<li><strong>Many pilots fail.</strong> A large share of multi-agent projects don’t survive their first months in
production, commonly because the team picked the wrong pattern, or the right pattern without
understanding its failure mode — a swarm with no hop cap loops; a fan-out with hidden cross-task
dependencies corrupts its merge.</li>
</ul>
<p>The corollary: the value isn’t “more agents,” it’s <strong>the right topology plus the resilience to survive
its failure mode</strong> — hop caps, idempotent handling, isolation. (We wrote up those mechanics in
<a href="/blog/recovering-from-agent-failures/">recovering from agent failures</a>.)</p>
<figure class="fig fig-inline"><img src="/blog/assets/media/multi-agent-orchestration-patterns/note-2.png" alt="Hand-drawn sketch from “Multi-Agent Orchestration Patterns: Which Topology, and When”" loading="lazy" decoding="async" /></figure>
<h2 id="the-2026-framework-landscape" tabindex="-1">The 2026 framework landscape <a class="anchor" href="#the-2026-framework-landscape" aria-hidden="true">#</a></h2>
<p>If you’re building this on a framework, the control-vs-simplicity tension hasn’t converged — they differ
mostly in orchestration model and ecosystem:</p>
<ul>
<li><strong>LangGraph</strong> — a directed graph with conditional edges; the most control, the most boilerplate. The
default for stateful, auditable, regulated workflows.</li>
<li><strong>CrewAI</strong> — role-based “crews” with process types; the fastest path to a working multi-agent team.</li>
<li><strong>AutoGen / AG2</strong> — conversational group chat between agents.</li>
<li><strong>OpenAI Agents SDK</strong> — explicit handoffs between agents, with a built-in execution sandbox.</li>
<li><strong>Claude Agent SDK / Strands</strong> — simplicity over fine-grained orchestration.</li>
</ul>
<p>The 2026 trend is convergence on common abstractions (graphs, roles, handoffs) with differentiation in
ecosystem depth and ops tooling. Pick for the orchestration model you need, not the logo.</p>
<h2 id="how-the-patterns-map-onto-a-hive" tabindex="-1">How the patterns map onto a hive <a class="anchor" href="#how-the-patterns-map-onto-a-hive" aria-hidden="true">#</a></h2>
<p>A concrete system makes the patterns less abstract. Munder Difflin runs several at once:</p>
<ul>
<li><strong>Orchestrator-worker / supervisor</strong> — the <a href="/blog/how-the-god-orchestrator-works/">god orchestrator</a>
classifies intent, decomposes it, dispatches to role-specialized agents, and owns integration. That’s
the 2026 default, made local and watchable.</li>
<li><strong>Blackboard</strong> — the shared board and the append-only event log are a blackboard the team reads and
writes.</li>
<li><strong>Fan-out</strong> — a broadcast message is scatter-gather over the active roster.</li>
<li><strong>Maker-checker</strong> — human-in-the-loop approval and adversarial review act as a consensus gate on risky
output.</li>
</ul>
<p>It’s the same lesson throughout: orchestration is how agents <a href="/blog/coordinating-ai-coding-agents/">coordinate without
colliding</a>, and the pattern you choose is a big part of whether they
do.</p>
<h2 id="pick-the-topology-then-make-it-survivable" tabindex="-1">Pick the topology, then make it survivable <a class="anchor" href="#pick-the-topology-then-make-it-survivable" aria-hidden="true">#</a></h2>
<p>The patterns aren’t exotic — they’re the small vocabulary of multi-agent design, and most systems are one
of them (or a couple composed). The skill is matching the topology to the problem’s dependency structure,
resisting the urge to over-architect, and then hardening whatever you chose against its specific failure
mode. A pattern without resilience is the project that fails in month three.</p>
<p>Want to watch the supervisor pattern run locally — a plain-language orchestrator decomposing your intent
across a team you can actually see? You can <a href="/#install">download Munder Difflin</a> free; it’s open source.</p>
<section class="faq" aria-label="Frequently asked questions">
<h2 id="faq">FAQ</h2>
<div class="qa">
<p class="q">What are the main multi-agent orchestration patterns?</p>
<p class="a">Six recur: orchestrator-worker (a.k.a. supervisor — a central agent decomposes and delegates), hierarchical (supervisors of supervisors), sequential pipeline (fixed linear stages), parallel fan-out (scatter-gather over independent tasks), debate/maker-checker (one agent produces, another verifies), and blackboard (agents coordinate through shared state). Most production systems lean on orchestrator-worker.</p>
</div>
<div class="qa">
<p class="q">Which orchestration pattern should I use?</p>
<p class="a">Match it to your dependency structure: linear dependencies → pipeline; independent tasks → fan-out; accuracy-critical work → maker-checker; known sub-tasks with one accountable owner → orchestrator-worker (the 2026 default). Start with the simplest pattern that fits — most teams over-architect and add agents they don't need.</p>
</div>
<div class="qa">
<p class="q">Is a multi-agent system always better than a single agent?</p>
<p class="a">No. In benchmarks, a single agent matched or beat multi-agent systems on a majority of tasks when given the same tools and context, and a large share of multi-agent pilots fail in production — usually from the wrong pattern. More agents add coordination cost; they pay off only when the task genuinely decomposes.</p>
</div>
</section>
<hr />
<div class="share">
<span class="lbl">Tags</span>
<a class="tag" href="/blog/tags/orchestration/">Orchestration</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</a><a class="tag" href="/blog/tags/concepts/">Concepts</a><a class="tag" href="/blog/tags/architecture/">Architecture</a>
</div>
</div>
<aside class="toc-rail" aria-label="Table of contents">
<div class="tt">On this page</div>
<ol>
<li class="lvl-2"><a href="#the-pattern-catalog">The pattern catalog</a></li><li class="lvl-2"><a href="#a-decision-framework">A decision framework</a></li><li class="lvl-2"><a href="#patterns-compose">Patterns compose</a></li><li class="lvl-2"><a href="#the-honest-part-multi-agent-isnt-free">The honest part: multi-agent isn’t free</a></li><li class="lvl-2"><a href="#the-2026-framework-landscape">The 2026 framework landscape</a></li><li class="lvl-2"><a href="#how-the-patterns-map-onto-a-hive">How the patterns map onto a hive</a></li><li class="lvl-2"><a href="#pick-the-topology-then-make-it-survivable">Pick the topology, then make it survivable</a></li>
</ol>
</aside>
</div>
<footer class="post-foot wrap"><div class="prevnext">
<a class="pn prev" href="/blog/the-multi-agent-cost-playbook/"><span class="k">← Older</span><span class="t">The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend</span></a>
<a class="pn next" href="/blog/mcp-security-tool-poisoning/"><span class="k">Newer →</span><span class="t">MCP Tool Poisoning: How to Secure the Model Context Protocol</span></a>
</div>
<section class="related">
<h2>Related in Orchestration</h2>
<div class="post-grid">
<article class="card t-orchestration">
<a class="thumb t-orchestration" href="/blog/deploy-automated-pr-reviewer-agent/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/deploy-automated-pr-reviewer-agent/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-06-10">Jun 10, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>7 min</span>
</div>
<h3><a href="/blog/deploy-automated-pr-reviewer-agent/">Deploy a PR Reviewer That Never Sleeps — In About One Prompt</a></h3>
<p class="dek">A how-to for standing up a fully automated PR-reviewing agent in Munder Difflin — one that reads your real source (not just the PR description), de-dupes noise, and only escalates what matters. With a real triage run that turned 22 duplicate firings into a clean v0.2.5 patch queue.</p>
<div class="foot">
<span class="tag kind">Orchestration</span>
<a class="more" href="/blog/deploy-automated-pr-reviewer-agent/" aria-label="Read: Deploy a PR Reviewer That Never Sleeps — In About One Prompt">Read →</a>
</div>
</div>
</article>
<article class="card t-orchestration">
<a class="thumb t-orchestration" href="/blog/claude-code-git-worktrees-vs-hive/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/claude-code-git-worktrees-vs-hive/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-06-04">Jun 4, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>5 min</span>
</div>
<h3><a href="/blog/claude-code-git-worktrees-vs-hive/">Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code</a></h3>
<p class="dek">Claude Code git worktrees vs a hive: when isolated worktrees suffice for parallel agents, and when you need memory, messaging, and an orchestrator on top.</p>
<div class="foot">
<span class="tag kind">Orchestration</span>
<a class="more" href="/blog/claude-code-git-worktrees-vs-hive/" aria-label="Read: Git Worktrees vs a Hive: Two Ways to Parallelize Claude Code">Read →</a>
</div>
</div>
</article>
<article class="card t-orchestration">
<a class="thumb t-orchestration" href="/blog/local-first-ai-agent-orchestration/" aria-hidden="true" tabindex="-1"><img src="/blog/assets/media/local-first-ai-agent-orchestration/hero.png" alt="" loading="lazy" decoding="async" /></a>
<div class="body">
<div class="meta">
<time datetime="2026-06-04">Jun 4, 2026</time>
<span class="dot" aria-hidden="true"></span>
<span>5 min</span>
</div>
<h3><a href="/blog/local-first-ai-agent-orchestration/">Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud</a></h3>
<p class="dek">How local-first AI agent orchestration works under the hood — the loop, mailboxes, scheduler, and audit log that coordinate a hive on one machine.</p>
<div class="foot">
<span class="tag kind">Orchestration</span>
<a class="more" href="/blog/local-first-ai-agent-orchestration/" aria-label="Read: Local-First AI Agent Orchestration: How a Hive Runs Without a Cloud">Read →</a>
</div>
</div>
</article>
</div>
</section>
</footer>
</article>
</main>
<footer class="site-foot">
<div class="wrap">
<div class="foot-top">
<a class="foot-brand brand" href="https://munderdiffl.in" aria-label="Munder Difflin home">
<img class="brand-logo" src="https://munderdiffl.in/logo.png" width="1318" height="840" alt="Munder Difflin, Inc. — Multi-Agent Harness" />
</a>
<div class="foot-links">
<a href="/blog/">Latest</a>
<a href="/blog/topics/">Topics</a>
<a href="/blog/about/">About</a>
<a href="https://munderdiffl.in/blog/feed.xml">RSS</a>
<a href="https://github.com/chaitanyagiri/munder-difflin">GitHub</a>
<a href="https://munderdiffl.in">munderdiffl.in ↗</a>
</div>
</div>
<div class="foot-meta">
© 2026 Munder Difflin · Local-first · MIT-licensed ·
Built on <a href="https://munderdiffl.in">Electron, React, Pixi.js, xterm.js & node-pty</a>.
Run an office of agents while you sleep.
</div>
</div>
</footer>
<script>
// sticky-nav border on scroll
(function () {
var nav = document.getElementById('nav');
if (!nav) return;
var onScroll = function () { nav.classList.toggle('scrolled', window.scrollY > 8); };
onScroll(); window.addEventListener('scroll', onScroll, { passive: true });
})();
// YouTube click-to-load: thumbnail button → youtube-nocookie iframe
(function () {
document.addEventListener('click', function (e) {
var btn = e.target.closest('.yt-load');
if (!btn) return;
var box = btn.closest('.yt');
var id = box && box.getAttribute('data-yt');
// Only an 11 character YouTube video id may reach the iframe URL.
if (!id || !/^[A-Za-z0-9_-]{11}$/.test(id)) return;
var frame = document.createElement('iframe');
frame.src = 'https://www.youtube-nocookie.com/embed/' + encodeURIComponent(id) + '?autoplay=1';
frame.title = box.getAttribute('data-title') || 'YouTube video';
frame.allow = 'accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share';
frame.setAttribute('allowfullscreen', '');
box.replaceChildren(frame);
});
})();
</script>
</body>
</html>