liveBook · Manning

Agent orchestration

As explained in Vibe Engineering

The coordination of models, tools, data flows, and execution steps into a larger workflow.

Five agents can finish tasks in parallel and still leave a developer untangling conflicting assumptions, stale tests, and interruptions. Agent orchestration moves some of that coordination from the developer to a system that decomposes work, assigns agents, sequences dependencies, and synthesizes results. Its potential comes from parallel execution and specialized roles, not necessarily better individual agents. section 5.6.3 section 5.6.7

Use a fleet when work is well understood and decomposable, not simply because multiple agents are available. Alternatives include running independent tasks side by side or using one agent that spawns subagents while preserving a single point of interaction. Exploratory work is a poor fit for a rigidly orchestrated team. section 5.6 section 5.6.7

A stale test handoff

An authentication agent and an API agent make conflicting interface assumptions, while a test agent starts before the implementation is ready. Parallel execution reduces waiting, but the developer must reconcile context and sequence the handoffs. An orchestrator aims to manage those dependencies rather than leaving the entire graph in the developer’s head. section 5.6.3

A bad artifact can propagate across several agents before anyone notices. Diagnosis then requires tracing causation across agent boundaries, while rollback must account for partial changes made under an invalid assumption. Policy enforcement also becomes harder because interactions, not just individual actions, matter. section 5.6.7

Treat orchestration as an operational system, not a shortcut around supervision:

  • Start with a conservative, predictable workflow and build observability before increasing autonomy. section 5.6.7
  • Plan for rollback across partial states and use sandboxing to limit the blast radius of mistakes. section 5.6.7 section 5.8
  • Retain the foundations needed for less autonomous agents, including the ability to judge a good diff and observe agent behavior. section 5.0 section 5.8

A dashboard is not necessarily an autonomous pipeline. As of early 2026, GitHub’s Agent HQ is described more as a command center than a fully autonomous pipeline orchestrator; Antigravity provides a manager surface for spawning and observing agents. Evaluate the actual coordination and governance available rather than assuming the interface supplies them. section 5.6.4

How Vibe Engineering covers it

How deep it goes
Explains coordination alternatives, failure modes, and operational guardrails without specifying an orchestration implementation.
Examples
Illustrates conflicting authentication and API assumptions, a test agent using stale artifacts, and agent-management platforms.
What it assumes
Assumes experience supervising agent-generated diffs and building observability before coordinating multiple agents.
What you can do after
Evaluate when to use an agent fleet and what operational controls its failures require.
How it connects
Connects orchestration to parallel execution, dependency management, observability, rollback, sandboxing, and policy enforcement.

Also explained in

Compare how 19 books explain agent orchestration →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.