Delegation

Delegation lets an agent send a self-contained task to a background subagent while it continues working. The subagent reports back to the parent agent, which incorporates the result into its response.

Enable delegation

Open the agent's Delegation settings and enable Dispatch sub-agents:

• Allow: the agent can dispatch without asking for approval.
• Ask: dispatch pauses for the user's approval.

The same setting governs resuming a subagent for follow-up work. Save and publish the agent to apply changes to users.

What a subagent receives

A subagent runs with the parent agent's configuration, but its task comes from a separate brief. It does not receive the parent conversation's transcript or the user's screen. The parent must include the facts and requirements the subagent needs in that brief.

Subagents use the parent's grants with these limits:

• Page-reading, navigation, highlighting, and form-prefilling tools are unavailable because the subagent has no browser client of its own.
• A subagent cannot dispatch or resume other subagents. Delegation is one level deep.
• A workspace is available only if the parent grants it, with the same repository-access setting.
• A subagent has no memory. Memory is private to each signed-in visitor, and a subagent runs with no memory store bound, so it does not search saved memories, write them, or extract new ones.

Delegating a task does not grant additional actions or override their policies.

Approvals during delegated work

An Ask setting on a tool or action still requires approval when a subagent calls it. The request is relayed to the user's conversation and identifies the subagent as the requester. The subagent waits for the decision before that operation proceeds.

A catalog action set to Deny is unavailable to the subagent, just as it is to the parent. See Actions for catalog policies and agent grants.

See Dispatches to inspect delegated work and Conversations to review the parent conversation.