cursor-subagents

The Cursor SDK has first-class subagents: declare them on AgentOptions.agents and the parent agent decides when to spawn them. This is not a manual orchestration layer — the parent's planner picks subagents based on their description.

When to use

• Splitting a workload into specialist personas (planner, coder, reviewer)
• Scoping a subagent to a subset of MCP servers
• Running subagents on a different model from the parent

Configuration

• [[references/agents-field]] — AgentOptions.agents: Record<string, AgentDefinition>
• [[references/agent-definition]] — description, prompt, model, mcpServers
• [[references/mcp-scoping]] — restricting tool access per subagent
• [[references/model-inheritance]] — "inherit" vs explicit override
• [[references/persistence]] — re-pass on Agent.resume

Observation

• [[references/task-events]] — SDKTaskMessage in the run stream

Cross-links

• MCP server names → [[../cursor-mcp/references/inline-config]]
• Models → [[../cursor-models/SKILL]]