liveBook · Manning

Chapter 8: Collaboration: When one agent is not enough

What you will learn in chapter 8 of Designing AI Agents

This introduction explains why collaboration helps when work can be divided, but adds costs that a single agent may avoid.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This introduction explains why collaboration helps when work can be divided, but adds costs that a single agent may avoid.

Key terms: lead agent, subagents, independent pieces of work, dependency shape, acceptance criteria, working context, coordination cost

8.1 What collaboration changes

The section defines collaboration as a transfer of responsibility between agents and gives three gates for deciding whether adding an agent is worthwhile.

Key terms: Collaboration, boundary between agents, decision state, shared storage, three gates, independent search areas, boundaries, separate authority, single-agent baseline, outcome quality

8.2 Pattern: Handoff Chain

Handoff Chain moves sequential work between specialists using an explicit package that preserves decision-critical state as ownership changes.

Key terms: handoff, condition, ownership, Handoff Chain, Collaboration × Chain, analyzer, implementer, verifier, typed packet, authoritative artifact

8.2.1 Walking through an airline-support handoff

This section walks through an airline-support handoff, showing what information must pass between agents, how a specialist returns a task, and why shared storage is not enough.

Key terms: triage agent, seat specialist, handoff, evidence of the action, Agent2Agent protocol, TASK_STATE_INPUT_REQUIRED, TASK_STATE_REJECTED, shared workspace, shared context, decision state

8.2.2 A chain in a coding agent

This section shows how a coding agent can coordinate isolated specialists in a handoff chain and when that split is worth making.

Key terms: top-level dialog, subagents, fresh, isolated context, handoff, specialists, responsibility, tools, permissions, role, relevant context

8.2.3 When Handoff Chain breaks

This section explains three ways a Handoff Chain can fail and how to limit each risk.

Key terms: information loss, handoff, package, missing evidence, framing propagation, weak diagnosis, evidence, invalidation conditions, independent investigation, sequential latency

8.3 Pattern: Fan-Out/Gather

This section explains how Fan-Out/Gather divides a task into independent concurrent branches and combines their results without losing coverage or conflicting evidence.

Key terms: Fan-Out/Gather, Collaboration × Parallel, hierarchical, branches, partition, duplicate work, return schema, completion policy, merge rule, contradictions

8.3.1 When apparent parallelism collapses

This section shows why adding workers does not create useful parallelism when they share a blocker, and how to restore independent work.

Key terms: shared failure, dependency graph, useful parallel work, GCC, known-good compiler, better partition, shared dependency

8.3.2 Gathering without hiding the minority

This section explains how to gather parallel workers’ findings without concealing disagreements or important findings reported by only one worker.

Key terms: gather step, underlying cause, incompatible recommendations, material finding, uncertainty, supervisor, learning loop, adjudicated, visual context

8.3.3 Parallel work in coding agents

This section explains how coding agents can work in parallel while controlling conflicts over shared resources and validating the combined result.

Key terms: Git worktrees, conflict domains, coordinator, work partition, write partition, gather point, integration tests

8.3.4 When Fan-Out/Gather breaks

This section explains how to recognize duplicate work and unresolved conflicts in Fan-Out/Gather, then check whether it improves on a single-agent approach.

Key terms: workers, evidence surfaces, claims, artifacts, deduplicate by cause, unresolved integration, concatenation, unconstrained synthesis, burden of proof, single-agent baseline

8.4 Pattern: Adversarial Review

This section introduces Adversarial Review as a bounded, evidence-driven exchange in which a reviewer challenges a writer’s claim and a judge decides what the evidence supports.

Key terms: writer, reviewer, judge, claim, changed artifact, independence, clean context, burden of proof, search boundary, decision rule

8.4.1 Three mechanisms that look like review

Distinguishes three kinds of inspection by the decisions they make and explains what makes a review genuinely adversarial.

Key terms: Generator-Critic, Adversarial Review, Approval Gate, independent security reviewer, judge

8.4.2 Evidence from code review systems

The section uses code-review systems to show the value and limits of independent critique, and when a test is a better choice than another reviewer.

Key terms: CriticGPT, defect claim, human judgment, Devin Review, clean context, wider task context, mechanically testable claims, Adversarial Review, counterevidence

8.4.3 Running a bounded review

This section explains how to assign distinct responsibilities, share review evidence without losing independence, and limit an adversarial review loop.

Key terms: writer, security reviewer, judge, safety claim, verdict, current artifact, review record, shared issue list, working contexts, review budget

8.4.4 When Adversarial Review breaks

This section explains three ways Adversarial Review can fail and how to keep findings useful, judgments independent, and review bounded.

Key terms: performative disagreement, affected claim, evidence, consequence, verdict changes, shared convergence, source of judgment, independence, endless review, burden of proof

8.5 Pattern: Hierarchical Delegation

Introduces Hierarchical Delegation as a way to coordinate dependent worker tasks under a manager that maintains the plan and integrates the results.

Key terms: manager, child agents, shared state, Hierarchical Delegation, bounded deliverables, explicit dependencies, global coherence, plan revision, Fan-Out/Gather, independent branches

8.5.1 What the manager and workers need from each other

This section explains what a manager must pass to workers and how workers should report problems that require the manager to revise a plan.

Key terms: overall goal, required interfaces, tool and write boundaries, expected artifact, acceptance checks, upward path, affected decision, evidence, independent reviewer, accountable human

8.5.2 Hierarchical delegation in coding agents

This section shows how coding-agent hierarchies delegate bounded work while keeping integration and permission boundaries with the manager and runtime.

Key terms: main dialog, bounded task, subagent configuration, expected artifact, tool boundaries, runtime, read-only tools, Guardrail Sandwich, LangGraph, Deep Agents

8.5.3 When Hierarchical Delegation breaks

Identifies where hierarchical delegation can fail and how to keep a manager’s plan, worker deliverables, and shared state reliable.

Key terms: manager, decomposition, acceptance criteria, local optimization, overall goal, required interfaces, boundary, cascading failure, artifact, shared state

8.6 Testing and observing collaboration

This section explains how to test whether a collaborating team improves task outcomes and how to trace coordination failures without mistaking a trace for proof of correctness.

Key terms: single-agent baseline, outcome measures, coordination measures, Handoff Chain, Fan-Out/Gather, Adversarial Review, Hierarchical Delegation, MAST, trace, claim

8.7 Composing collaboration patterns

Shows how a code release can combine four collaboration patterns at different stages, with explicit handoffs between them and no pattern added without a need.

Key terms: Hierarchical Delegation, Fan-Out/Gather, Adversarial Review, Handoff Chain, partition, write-conflict domain, return schema, completion policy, independent evidence, stop rule

8.8 The implementation layers: Where control lives

The section separates where collaboration is implemented from the choice of how agents divide responsibility.

Key terms: control point, current plan, shared state, framework, runtime, harness, Deep Agents, collaboration pattern

8.8.1 Three communication channels

Distinguishes three communication channels in agent collaboration and clarifies the human accountability they require.

Key terms: agent to agent, human to agent, human to human, RFC, ADR, runbook, accountable human owner, human intervention, durable records

8.8.2 MCP and A2A are the plumbing

This section distinguishes two communication protocols and explains why collaboration architecture must be chosen before protocol plumbing.

Key terms: Model Context Protocol, Agent2Agent, tools and data, tasks and results, collaboration pattern, architecture decisions, tool access, task exchange

8.9 Argus checkpoint: Collaboration

This checkpoint describes the collaboration Argus can perform, marks what it cannot yet do, and cautions that coordination does not guarantee a correct plan.

Key terms: security, style, and complexity workers, structured findings, gather point, Adversarial Review, manager, multi-stage release plan, Handoff Chain, coordination

8.10 Summary

8.11 References

Lists the sources cited in the chapter on agent collaboration.

Where this is used later

Concepts explained in this chapter

← Chapter 7: Reflection and evaluation: How your agent audits and learns from itself Chapter 9: Governance: Constraints that enable freedom →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.