Skip to content
Everruns Everruns

Sub Agents

IDsubagents
CategoryCore
Featuressubagents
DependenciesNone

Spawn subagents for parallel task execution. Each subagent runs in its own isolated context window, allowing the parent agent to delegate verbose or independent tasks without cluttering the main conversation. Subagents inherit the parent’s harness and agent configuration but operate with their own message history.

Tools

Section titled “Tools”

spawn_subagent

Section titled “spawn_subagent”

Create and start a new subagent. The subagent begins executing immediately. Returns a task_id that can be used with the generic session task tools to monitor, message, or cancel the subagent.

ParameterTypeRequiredDescription
namestringyesHuman-readable name for the subagent. Must be unique within the session.
instructionsstringyesInstructions for what the subagent should do. This becomes the subagent’s initial prompt.
blueprintstringnoOptional specialist blueprint ID, such as github_scout, that supplies its own prompt, model, and private tools.
configobjectnoBlueprint-specific configuration. Only valid when blueprint is set.

Managing subagents after spawn

Section titled “Managing subagents after spawn”

Use the generic session_tasks tools to monitor and steer subagents after spawning. The task_id is returned by spawn_subagent.

  • list_tasks with kind: "subagent" — list all subagent tasks and their status
  • get_task with the task ID — get detailed status and result for a specific subagent
  • message_task — send a steering message or additional context to a running subagent
  • cancel_task — request cooperative cancellation of a subagent
  • wait_task — block until a subagent reaches a terminal or interrupted state

Notes

Section titled “Notes”
  • No nesting — subagents cannot spawn other subagents.
  • Foreground mode — spawning blocks until the subagent completes. Foreground execution has a 5-minute timeout.
  • Inherited configuration — subagents inherit the parent’s harness and agent configuration.
  • Blueprints — specialist blueprints can run with their own prompt, model, and private tools while still using the same subagent lifecycle.

See Also

Section titled “See Also”