13. Multi-Agent Value Is Not Multiple Models Running

Copying the same conversation to three models and running them together adds concurrent model calls. It does not automatically solve task decomposition, context contamination, permission inheritance, or conflicting results.

A child Agent adds a delegation boundary.

The minimum task packet

“Analyze the logs” leaves scope undefined. Copying the entire parent conversation transfers irrelevant material and permissions.

Isolation reduces two costs

First, it reduces Tokens: the child receives only relevant files and rules rather than full parent history.

Second, it reduces interference: abandoned approaches, unrelated modules, and private material remain outside the task. Isolation does not hide necessary information; it makes necessary information explicit.

Permission shrinks during delegation

A parent with repository write access does not grant that access to a log-analysis child. A child returning “run this command” has not gained execution permission; the parent revalidates the action.

The parent verifies results

The parent checks specified inputs, task boundaries, output structure, evidence existence, and conflicts among children. Majority vote cannot replace evidence. Different conclusions may come from different inputs or a missed constraint.

Parent and child traces remain connected

Delegation creates a child trace_id and records parent trace, parent turn, and delegation event. Tool events remain in the child trace. A structured delegation.completed result returns to the parent.

This allows cost accounting per child and provenance from a parent conclusion back to its source. Flattening all events into one conversation erases budget and permission boundaries.

Merging is work

The parent resolves duplicate facts, conflicting conclusions, evidence collected at different times, and incomplete items. The merge event records accepted, rejected, and review-required claims rather than only the final summary.

If validation and merging cost approaches the cost of the subtask, delegation has no net benefit. Evaluation includes the parent’s decomposition, waiting, verification, and merge Tokens.

Tasks that should remain single

Short tasks, strongly sequential tasks, and tasks sharing one mutable resource often cost more to coordinate than to execute. If three children continuously need each other’s newest state, the work was not independently delegated.

The experiment

Run one task in three modes: one Agent, full-context copies, and minimum task packets. Compare total input Tokens, completion time, repeated reads, unauthorized actions, conflicting results, and parent verification time.

Multi-Agent value is demonstrated by net gains from isolation and safe parallelism, not by the number of models shown as active.

Value follows task structure

net value = parallelism and isolation
          - delegation, communication, verification, and merge cost

Highly coupled work on changing shared code can spend more on synchronization than it saves. Three identical models using the same incorrect evidence also have correlated errors; majority voting does not create independence.

A 2026 study comparing independent, centralized, decentralized, hybrid, and single-Agent configurations found that stronger models can reduce collaboration gains and that task structure determines scaling behavior. Capable language models can outgrow the benefits of collaboration

A2A-style interoperability exchanges capability cards, tasks, messages, and artifacts. It does not establish trust. Receivers still authenticate identity, scope, claims, and provenance.

Compare one Agent, full-context sharing, minimal task packets, and independent-method verification. Include wall time, cumulative Tokens, duplicate reads, conflicts, merge time, permission scope, and correctness.