Start With One Agent

One agent with a handful of good tools is the right first design. It's cheaper, and there's one context to read when something goes wrong. For a task that needs one kind of skill, it's also the right last design. Splitting the work is worth considering once that agent holds so many tools and instructions that it does every part half well.

Give one agent research, planning, coding, review and deployment, and you get a very long system prompt, a pile of tools and mediocre results at every step. Instructions compete for attention, the wrong tool gets picked, and the agent loses track of what it already found.

Splitting the work across specialist agents can fix that, but it is not free: more tokens, more hand-offs, and failures that pass from one agent to the next. The patterns below (orchestrator, supervisor and swarm) differ mostly in how they coordinate, and picking the wrong one costs more than staying with a single agent.

Signs you have outgrown one agent
  • Your single-agent system works for demos but produces mediocre output on complex, multi-step tasks
  • You've seen the "agent swarm" videos on Twitter and wonder if that's actually how production systems work
  • You tried chaining multiple LLM calls and the context window exploded after 3 rounds
  • You want multi-agent but have no idea which pattern fits your use case