An architect is deciding where a lead agent with parallel subagents is worth its extra token cost. Which workload fits that architecture best?
Choose an answer to check it. Afterward, select any option to review its explanation.
Multi-agent runs use far more tokens than chat, so they only make sense when the task's value covers that cost.
Multi-agent systems pay off on valuable, heavily parallel work whose information exceeds a single context window: subagents explore separate directions at once, each in its own context.
Parallel subagents are overkill for a simple lookup. One agent with a few tool calls covers it.
Code changes look like divisible work, which makes this tempting. But tightly coupled steps need shared context, and agents are not yet good at coordinating in real time, so this is named as a poor fit.
id q179816f9df