OrchestriAI
All terms

Subagent

A separate AI agent session that a main agent starts for one task, with its own context window, instructions and tools, which returns a short report when done.

Want agents that hand off side work cleanly?

Free. Three short fields, and we reply by email within one business day.

Technical details checked 2026-10-29

Concept map

Follow the connections to see how the term fits into a broader automation system.

In one sentence

A separate AI agent session that a main agent starts for one task, with its own context window, instructions and tools, which returns a short report when done.

A subagent is a helper agent that a main agent, often called the parent or orchestrator, starts to handle one piece of work. The subagent runs in its own session with its own context window, its own system prompt, and usually a narrower set of tools and permissions. When it finishes, it sends back a summary instead of everything it read and ran along the way.

Why subagents exist

Every model has a fixed context window, and the more that window fills with search results, logs and file contents, the harder it is for the model to keep track of what matters. Anthropic's engineering team calls this context rot. Handing noisy side work to a subagent keeps the main conversation focused on planning and decisions. Anthropic describes sub-agents that explore in depth and return condensed summaries of roughly 1,000 to 2,000 tokens.

Where you see them

Coding tools ship subagents by default. Claude Code lets you define subagents with their own prompts, tools and permissions, and suggests using one when a side task would flood the main conversation. OpenCode includes built-in General and Explore subagents and lets teams define their own. Business agents use the same pattern, for example one subagent that researches a lead while another drafts the email.

What to watch

A subagent only knows what its assignment tells it, so a vague brief produces a vague result. Default subagents are usually one-way: the child cannot ask the parent a question mid-task, and the parent cannot redirect it. Parallel subagents that write to the same files will conflict unless each one works in its own branch or git worktree. Subagents also use model tokens, so spreading work across many of them costs more than it might look.

In practice

Give each subagent a complete assignment, the narrowest permissions it needs (a reviewer should be read-only), and a clear report format. Review what comes back before acting on it. Our open-source OpenCode Smart Subagents plugin adds two-way messages, mid-run steering and worktree isolation to OpenCode's subagents; it is listed on our projects page.

Keep following the system

Free. Three fields. We reply within one business day.

Want agents that hand off side work cleanly?

We design subagents with clear briefs, narrow permissions and reports your main agent can trust.

You'll talk to Shariq. Replies come from shariq@orchestriai.com. Leave out passwords and patient records.

What happens next

  1. 1.You send one line about the task.
  2. 2.Shariq reads every message and replies by email within one business day.
  3. 3.If it fits, you get a written plan or a short call. Your choice.
  4. 4.If it does not fit, we tell you and point you to a better option.
“Shariq built our Open Dental to GoHighLevel sync and our AI routing system for new patient inquiries. Both projects were delivered fast, worked right away, and he was responsive whenever we needed adjustments. He understands dental practice workflows and doesn't overcomplicate things.”
Michael Ling, Owner, Smile Again Dental