Research

AI Agent Swarm Playbook 2026

How AI agent swarms are built, broken, and paid for. Researched and written by a swarm itself: 55+ agents, 537 sources, one night.

Built by an agent swarm in one night
537
sources
147
verified claims
55+
agents
12
chapters

In brief — for those who decide

The question stopped being whether to adopt agentic AI. It's where it pays off — and where it quietly burns budget. This research answers the second question with numbers, not promises.

By 2027, more than 40% of agentic projects will be cancelled — almost always because the swarm was pointed at the wrong task. We built the map of that decision: 12 chapters, 537 sources, 147 key claims, and a second agent re-checked every one of them, briefed to refute rather than rubber-stamp. Contested figures are flagged right in the text.

How it happened

A study of multi-agent systems, executed by a multi-agent system: 55+ agents orchestrated by a single human, 51 logged runs, four phases — research, verification, writing, selection.

The first run hit a concurrency ceiling: a monolith of 43 agents had to be re-sharded into parallel workflows on the fly. The episode was not cut from the report — it became the illustration for the failure-modes chapter.

The telemetry is open: the logbook records every run and every tool call. A control experiment is included — the same survey written by a single agent with no sources.

Three techniques from the edition

Each technique links to an open chapter where it is worked through in full.

Alongside the text

Why this is different

55+ agents

A swarm studying swarms

Not a model reciting from memory, not an essay about the future. This research on multi-agent systems was executed by a multi-agent system: 15 researchers, adversarial fact-checkers, 12 parallel writers, an idea-selection panel, a final critic. The method is described in the book — and demonstrated by its existence.

23% corrected

Every number checked by a second agent

147 key claims went through independent verification — and the verifier's brief was to disprove, not confirm. The verifiers corrected 34 of the 147 claims (23%) made by their own researchers — and that counter is published. The verification dataset is machine-readable.

Fragility registry

Honesty as an architectural principle

The weakest spots are collected in a dedicated “fragility registry”; single-sourced cases are flagged in the text. An admitted error is antifragile; a hidden one is waiting for a screenshot.

The 12 chapters — a map

Three chapters are fully open — no sign-up. Free registration unlocks the other nine.

EN edition: rolling translation — chapters are being translated; open chapters are readable now (Russian original inside).

  1. 0111 minRead

    The 2026 Landscape

    The framework market consolidated hard: one lab, one blessed framework.

    2 of the 3 most-downloaded agent SDKs still have no version 1.0

  2. 0213 minRead

    Orchestration Patterns

    The only architecture with strong production evidence is orchestrator-worker; everything else comes with caveats.

    +90.2% over a single model (Anthropic)

  3. 0311 minSign-up required

    Swarm Economics

    A swarm is a way to spend more compute in parallel — and it doesn't pay off everywhere.

    a 16-agent swarm wrote a 100,000-line C compiler for under $20,000

  4. 0410 minRead

    Why Swarms Fail

    Failures are system design bugs, not “dumb models.”

    41–86.7% of runs end in failure (MAST, 1,642 traces)

  5. 0514 minSign-up required

    Protocols

    The standards war ended in layering: MCP for tools, A2A for agents.

    ~97M monthly MCP SDK downloads

  6. 0610 minSign-up required

    Fleet Security

    Prompt injection is unsolved — design for blast radius, not filters.

    microVM isolation costs ~125 ms and <5 MiB per agent (Firecracker)

  7. 0710 minSign-up required

    Memory and Context

    A long-lived swarm survives on context discipline, not a bigger window.

    cached input is ~10× cheaper — KV-cache hit rate is metric #1

  8. 089 minSign-up required

    Observability and Evals

    Judging an agent by its final answer is systematic flattery.

    outcome-only evaluation overstates quality by 20–40%

  9. 098 minSign-up required

    Production Case Studies

    What actually shipped in 2025–2026 — and what got rolled back.

    Devin lifted its merge rate from 34% to 67% in a year

  10. 1010 minSign-up required

    Humans and the Swarm

    The industry converged on “many agents, one screen” — and hit the wall of human review.

    6 major vendors converged on the fleet interface within 10 months

  11. 1111 minSign-up required

    The Academic Frontier

    Most “multi-agent advantages” are compute, diversity, and aggregation — not collaboration.

    a panel of 9 AI judges yields ~2 effective votes

  12. 1211 minSign-up required

    Recommendations for Self-Hosted Fleets

    Common self-hosted agent fleet decisions cross-checked against 2025–2026 market data.

    the anti-microVM argument is ~100× overstated (real overhead <5 MiB)

How it was made

The telemetry is open — the timeline.json logbook records every launch.

51 logged agent runs

Across four phases: 17 research (including two restarts after the 43-agent monolith was aborted), 14 verification, 12 writing, 8 panel. Plus the orchestrator, the final critic, and the demo engineer — 55+ in total.

~40 min for the core phases

The first researcher launched at 00:46 UTC; the panel finished at 01:27. Peak: 10 researchers running concurrently; 12 chapters written in parallel, most in ~3 minutes.

~4M tokens, 1,060+ tool calls

Mostly web search and source reading.

Drama is part of the report

The first run hit a concurrency ceiling; the orchestrator re-sharded the swarm on the fly from a monolith into 5 parallel workflows — an episode that became a live illustration of the failure-modes chapter. A control experiment is included: the same survey written by a single agent with no sources.

10 findings on AI agent swarms — in 5 minutes

Every number below was independently checked by a second agent; contested ones are flagged. Full reasoning lives in the 12 chapters.

  1. 01

    A swarm is a way to spend more compute in parallel — not a “hive mind.”

    Per Anthropic, token volume alone explains 80% of a multi-agent system's quality variance on the BrowseComp benchmark. Topology and “smart collaboration” are secondary: you are buying parallel compute, not magic.

    Source: Anthropic, How we built our multi-agent research system, 2025

  2. 02

    Orchestrator-worker is the only pattern with strong production evidence.

    Anthropic's multi-agent research system beat a single model by 90.2% — while burning roughly 15× the tokens of a chat. The pattern works for broad parallel reading, not for coupled coding.

    Source: Anthropic, 2025-06-13

  3. 03

    The read/write rule decides everything.

    Reads — research, review, search — parallelize them. Writes — code, synthesis, coherent text — keep them single-threaded. Even public opponents converged here: Cognition (“Don't Build Multi-Agents”) and Anthropic, after their June 2025 dispute.

    Source: Cognition; Anthropic, 2025

  4. 04

    Swarms fail on 41–86.7% of runs — and the causes are organizational.

    The MAST taxonomy (1,642 annotated traces, 7 frameworks) attributes ~44% of failures to specification defects, ~32% to inter-agent misalignment, ~24% to weak verification. These are system design bugs, not “dumb models” — which means they are fixable by engineering.

    Source: UC Berkeley, MAST, NeurIPS 2025

  5. 05

    Debate and “panels of 9 judges” mostly did not survive replication.

    Correlated judge errors destroy ~75% of a panel's nominal “independence”: 9 judges yield roughly 2 effective votes. Prompt optimization delivers about twice the gain of topology optimization. The best place for extra agents is verification, not generation.

    Source: Nine Judges (Apple, 2026); MASS (ICLR 2026); Weaver (NeurIPS 2025)

  6. 06

    Swarm economics comes down to model tiers and KV-cache.

    Prices within model families span roughly 10×, which makes “cheap scouts + expensive judges” a working pattern. Cached input costs about 10× less than uncached — so KV-cache hit rate becomes production metric #1.

    Source: Vendor pricing, 2026; Manus, Context Engineering, 2025

  7. 07

    A budget must block the call, not send an alert.

    A documented two-agent loop burned ~$47,000 over 11 days — with dashboards up and running. Spending limits must stop the call before it is sent, at the infrastructure level. The case is single-sourced and honestly flagged in the study's fragility registry.

    Source: The playbook's fragility registry (single-sourced case)

  8. 08

    The protocol war ended in layering: MCP for tools, A2A for agents.

    MCP became the de facto standard of the agent-to-tool layer: ~97M monthly SDK downloads, 10,000+ active servers. Both protocols moved under neutral Linux Foundation governance — vendor capture is off the table. The open problem is security: MCP server supply chains are already being attacked.

    Source: Anthropic / Linux Foundation, December 2025

  9. 09

    Prompt injection is unsolved — build for blast radius, not filters.

    The “lethal trifecta” — private data, untrusted input, and an external channel — must never assemble in one agent. Isolation is nearly free: a microVM boots in ~125 ms with under 5 MiB of overhead. Injections already self-replicate agent-to-agent.

    Source: Willison, 2025; Firecracker; Prompt Infection (UCL/Stanford, 2024)

  10. 10

    Failure is the base case; plan the rollback before launch.

    74% of enterprises have already rolled back a live customer-facing AI agent (n=2,527), and Gartner expects over 40% of agentic projects cancelled by end of 2027. Meanwhile Devin lifted its merge rate from 34% to 67% in a year: where a swarm fits the task, it pays. The difference is rollback triggers defined in advance.

    Source: Sinch, 2026; Gartner, 2025; Cognition, 2025

Verified claims registry

The study's 147 key claims with adversarial-verification verdicts and source links. Each claim is an atomically quotable block with a permanent anchor.

Showing 12 of 147

  1. 01ConfirmedR01-frameworks

    LangGraph 1.0 GA 2025-10-22, no-breaking-changes-until-2.0 pledge; 64.7M PyPI downloads/mo (langgraph alone); users Uber, LinkedIn, Klarna, JPMorgan, BlackRock, Cisco (+Rippling)

    Source: changelog.langchain.com
  2. 02ConfirmedR01-frameworks

    Microsoft Agent Framework: preview 2025-10-01, RC 2026-02-19, 1.0 GA 2026-04-03; SK+AutoGen in maintenance mode; AG2 ~555K/mo vs CrewAI 11.4M/mo

    Source: devblogs.microsoft.com
  3. 03CorrectedR01-frameworks

    OpenAI Agent Builder + Evals deprecation notices 2026-06-03/04, sunset 2026-11-30, migration to code-first Agents SDK; SDK #2 at 30.8M/mo, still 0.18.x

    Source: therouter.ai
  4. 04CorrectedR01-frameworks

    Claude Agent SDK 22.0M/mo (third overall) at v0.2.x; H1-2026 subagent fan-out + Outcomes grading (+8.4%/+10.1% Word/PowerPoint)

    Source: claude.com
  5. 05ConfirmedR01-frameworks

    A2A to Linux Foundation (June 2025), v0.3 with gRPC + signed security cards (2025-07-31), 150+ orgs; ADK GA in Python/Go/Java/TS at 15.5M/mo

    Source: linuxfoundation.org
  6. 06ConfirmedR01-frameworks

    n8n valuation doubled to $5.2B via SAP strategic investment 2026-05-12, embedded in Joule Studio; 1,400+ enterprise customers, 1.7M monthly active builders; 196K GitHub stars

    Source: bloomberg.com
  7. 07ConfirmedR01-frameworks

    Mastra: 1.0 Jan 2026 at 300K weekly npm downloads; $22M Series A led by Spark Capital 2026-04-09 ($35M total); @mastra/core 1.11M/week by Jul 2026 (3.7x); users Brex, Sanity, Factorial

    Source: mastra.ai
  8. 08ConfirmedR01-frameworks

    CrewAI: 55.4K stars (most-starred pure agent framework), 11.4M/mo downloads, 60-63% F500 + ~2B executions/yr (vendor-reported, unaudited), $18M total funding, ~$3M est. revenue

    Source: siliconangle.com
  9. 09ConfirmedR02-anthropic-practices

    Orchestrator-worker Research architecture (Opus 4 lead + Sonnet 4 subagents, own context windows) beat single-agent Opus 4 by 90.2% on internal eval; post dated 2025-06-13

    Source: anthropic.com
  10. 10ConfirmedR02-anthropic-practices

    Agents ~4× / multi-agent ~15× chat tokens; token usage alone explains 80% of variance (95% with tool calls + model choice, BrowseComp); parallelism cut research time up to 90%

    Source: anthropic.com
  11. 11ConfirmedR02-anthropic-practices

    Effort-scaling rules (1 agent/3–10 calls; 2–4 subagents ×10–15 calls; >10 subagents) as one of exactly eight named prompt-engineering principles

    Source: anthropic.com
  12. 12ConfirmedR02-anthropic-practices

    "Building Effective Agents" 2024-12-19, Schluntz & Zhang, workflows-vs-agents taxonomy, five workflow patterns, "simplest solution possible"

    Source: anthropic.com

What's next

Companion tool

F/ONE Verdict

The verdict engine runs on this playbook's numbers: the same economics, the same failure modes, the same thresholds. Describe your task in nine steps and get a verdict plus a link to the chapter it is derived from.

How to read on

  1. 1

    Read the free chapters

    The executive summary, the claims registry, and three full chapters — free, no sign-up.

  2. 2

    Get the full version

    12 chapters, reading progress sync, living-document updates, PDF — soon. Free with registration.

  3. 3

    Audio version — coming soon

    Per-chapter narration and a podcast overview. Leave your email — we'll write first.

    Coming soon

Author

Vyacheslav Fedoseev

Vyacheslav Fedoseev

AI advisor to C-suite executives. Designs and deploys agent systems; consults leadership teams on AI strategy. Founder of F/ONE — “AI for those who decide”: no hype, numbers and checkable sources.

Who orchestrates the swarm

Briefings for those who decide

Once a month — what changed in agentic swarms and what it means for your decisions. Short, with numbers and sources.