Overview
Sub-agents are specialized agents you can delegate to. Each runs in its own isolated context with a restricted toolset, so the main conversation stays focused while a sub-agent handles a self-contained task — exploring the codebase, reviewing a change, or any role you define.Delegate by @mentioning a sub-agent in the composer, or by using one as a node inside a Workflow. A sub-agent’s full transcript opens in its own detail window.
What You Can Configure
Create and edit sub-agents in Settings → Extensions → Agents.| Field | Description |
|---|---|
| Name | Canonical kebab-case identifier (e.g. codebase-analyzer) |
| Display name | Human-readable label shown in the UI |
| Role | One-line description shown to the main model |
| System prompt | The instructions that define the sub-agent’s behavior |
| Allowed tools | The tool allowlist for this sub-agent |
| Permissions | Per-capability allow / ask / deny overrides |
| Model | Optional model override (otherwise inherits the parent’s) |
| Max iterations | Cap on the sub-agent’s steps per delegation |
| Icon & color | Optional SF Symbol and accent color |
Sub-agents cannot dispatch other sub-agents — delegation is one level deep, which keeps runs predictable.
How Delegation Works
Create the sub-agent
Define its role, system prompt, allowed tools, and permissions in Settings → Extensions → Agents.
It runs in isolation
The sub-agent works with its own tools and context, then returns a result to the main conversation.
Related
Workflows
Compose sub-agents into multi-step graphs with evaluators, breakpoints, and checks.