delegate_parallel
Run independent tasks as parallel sub-agents and get all reports in one answer. Ideal for non-dependent work; failed tasks are flagged without affecting other results.
Instructions
Run several independent sub-agents at once and return every report in one answer.
This is the tool to use whenever the work splits into pieces that do not depend on each
other: "summarise each of these four modules", "check these three services for the same
misconfiguration", "for each failing test, find the cause". Running them concurrently on
one NIM connection is much faster than calling delegate in a loop, and all the reading
still happens outside your context.
Every string in tasks is a separate cold-start sub-agent with no memory of the others
and no view of this conversation. Do not chain them - task 2 cannot use task 1's answer.
If the work is genuinely sequential, use delegate one step at a time. Each task string
must be self-contained and say what output you want, exactly as for delegate.
Parameters: tasks - list of self-contained task strings, one sub-agent each. profile - "general" (default), "researcher", "coder", or "reviewer"; applies to all. files - paths handed to every sub-agent up front. model - override the NIM model (default stepfun-ai/step-3.7-flash).
Concurrency is capped at SUBMCP_MAX_PARALLEL (default 4); extra tasks queue. All
sub-agents are read-only here - there is no write parameter, because concurrent edits
to one working tree are how you lose work. Use delegate with write=True for edits.
Returns one markdown document with a ## Task N section per input task, in the order you
supplied them. A task that fails gets its own section marked FAILED with the reason; the
other reports still come back intact, so one bad task never costs you the rest.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | No | ||
| model | No | ||
| tasks | Yes | ||
| profile | No | general |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |