Practice vocabulary for multi-agent systems: orchestrator agents, subagents, handoffs, communication protocols, and LangGraph workflows.
0 / 5 completed
1 / 5
Your architecture doc says 'The orchestrator agent delegates to subagents.' What is the role of the orchestrator?
In a multi-agent system, the orchestrator agent acts as a coordinator — it receives the top-level goal, breaks it into subtasks, dispatches those to specialized subagents, and combines their outputs into a final result.
2 / 5
A colleague says 'We need an agent communication protocol.' What does this define?
An agent communication protocol specifies how agents exchange information — what message format they use, how results are structured, and how one agent hands off context to another. Without a clear protocol, agents can misinterpret each other's outputs.
3 / 5
The system log shows 'The subagent reports back with a result: {status: success, data: [...]}.' What happens after the subagent reports back?
When a subagent completes its task and reports back, the orchestrator processes the result — deciding whether to call another subagent, ask for clarification, or synthesize a final response for the user.
4 / 5
Your team says 'We use LangGraph for the multi-agent workflow.' What does LangGraph provide?
LangGraph is a framework built on top of LangChain that models agent workflows as graphs — nodes are processing steps (agents or functions) and edges define the flow between them, including conditional branching and loops.
5 / 5
A design document mentions 'agent handoff vocabulary.' A handoff occurs when:
An agent handoff is when responsibility for a task is transferred from one agent to another — along with the accumulated context, state, and any instructions needed for the receiving agent to continue seamlessly.