agent_handoff

Parameters schema

{
  "type": "object",
  "required": [
    "task_description"
  ],
  "properties": {
    "mode": {
      "enum": [
        "sync",
        "async"
      ],
      "type": "string",
      "default": "sync",
      "description": "Execution mode: 'sync' (wait for result, default) or 'async' (fire and forget, child runs in background). Async is only available in background/trigger context."
    },
    "agent_id": {
      "type": "integer",
      "description": "Optional ID of another agent in the same workspace to delegate the task to. When set, this becomes cross-agent delegation; the target agent runs with ITS OWN prompt, tools, and model. Use this for specialty tasks (see agents.list to discover specialists). Prefer the in-loop variant (no `agent_id`) for one-off escalations. Spawns a new trace linked back to this trace via parent_trace_id (visible in the admin lineage card)."
    },
    "target_slug": {
      "type": "string",
      "description": "Optional stable slug of a system-template specialist to delegate to (e.g. 'doc-composer' for the Document Composer). Env-portable alternative to agent_id — resolves the workspace's fork of that template (auto-forking on first use). Used by async handoffs that target a specialist without knowing its per-workspace id."
    },
    "task_description": {
      "type": "string",
      "description": "Plain-language description of what the planner should accomplish. Include everything the planner needs: the user's goal, constraints, and any context already gathered in this voice call."
    }
  }
}

No endpoints wrapped at confidence ≥ 0.70.

Parent server