Skip to slide
101 / 170

CH 11 · Subagents and Multi-Agent Orchestration · 02/11

Read as one page

Built-in subagents

Cursor ships three built-in subagents, chosen by analyzing where context limits got hit:

SubagentJobWhy isolate it
ExploreSearch and analyze the codebaseGenerates large intermediate output; uses a faster model to run many parallel searches
BashRun a series of shell commandsCommand output is verbose; isolating it keeps the parent focused on decisions, not logs
BrowserDrive a browser via MCP toolsProduces noisy DOM snapshots and screenshots; the subagent filters to relevant results

Notice the model-flexibility trick: the Explore subagent uses a faster, cheaper model by default, so it can run ten parallel searches in the time one main-agent search would take. That ties back to pillar 5, tiered execution: use a cheap model for the grunt work and reserve the expensive one for the hard reasoning.

Finished this idea?

Your learning progress stays in this browser.