Delegate work to background subagents by passing multiple items in a single tasks[] batch. Execution does not block — you receive IDs immediately.Delegate work to ONE background subagent per call. Execution does not block — you receive an ID immediately. Agents marked BLOCKING run inline — results return in this call; non-blocking items in the same batch still spawn as background jobs.Run subagents synchronously by passing items in a tasks[] batch. Execution blocks until all work finishes.Run ONE subagent synchronously. Execution blocks until work finishes.

Async Job Contract

• Results auto-deliver. A settled hub jobs/hub wait snapshot is the delivery; no duplicate async-result follows.
• Job IDs are process-local and expire roughly five minutes after settlement. Afterward, use the agent ID with hub send, agent://<id>, or history://<id>.
• completed means successful yield/job exit, not artifact acceptance. Verify claimed changes.

Task Design

• Agent typing: Pick each item’s agent type. Read-only research MUST use agent: "scout" (faster model). Use default worker only when no specialist fits.
• No overhead: Each task MUST instruct its agent to skip formatters, linters, and project-wide test suites. Run those once at the end.
• One-pass: Prefer agents that investigate AND edit in one pass; spin a read-only scout only when affected files are genuinely unknown.
• Overlap is safe: Concurrent edits to the same files auto-resolve; worst case, agents coordinate directly over IRC. NEVER shrink or serialize a batch to avoid file overlap. Two prerequisites:
  1. Every task MUST skip validation (build/lint/tests) — validating mid-flight blocks agents on each other’s edits.
  2. Decide cross-task contracts up front (e.g. the interface A implements and B consumes) and state them in the batch contexttask, not left for agents to negotiate.

Inputs

• context: Shared project state, constraints, and contracts. Applies to the entire batch; do not duplicate this background into individual tasks.
• tasks[]: Array of subagents to spawn.
  • name: A stable CamelCase identifier (≤32 chars), used to address the agent (IRC, job ids). Generated automatically if omitted.
  • agent: The agent type running this item (e.g. scout, reviewer). Omitting it gives you the general-purpose worker (``) — NEVER pass that name explicitly. Only omit it after checking the agent list below and finding no specialist that fits. Current spawn policy allows: .
  • task: Complete, self-contained instructions. One-liners or missing acceptance criteria are PROHIBITED.

  • effort: Scale w/ complexity of this task: "lo"

    "med"

    "hi"

  • blocking: Per-call execution override — true runs this item inline (parent waits on its result), false forces a background job; omitting it follows the agent’s declared mode.
  • outputSchema: Invocation-specific JSON Schema. Overrides the selected agent and parent-session schemas.

  • schemaMode: "permissive" (default) accepts a retry-exhausted invalid result with a warning; "strict" fails it.

  • isolated: Run in a dedicated worktree; successful changes are automatically applied to the parent checkout.

  • isolated: Run in a dedicated worktree; changes are retained as patch or branch artifacts without modifying the parent checkout.
• name: A stable CamelCase identifier (≤32 chars), used to address the agent (IRC, job ids). Generated automatically if omitted.
• agent: The agent type to spawn (e.g. scout, reviewer). Omitting it gives you the general-purpose worker (``) — NEVER pass that name explicitly. Only omit it after checking the agent list below and finding no specialist that fits. Current spawn policy allows: .
• task: Complete, self-contained instructions. One-liners or missing acceptance criteria are PROHIBITED.

• effort: Scale w/ complexity of this task: "lo"

  "med"

  "hi"

• blocking: Per-call execution override — true runs this spawn inline (parent waits on its result), false forces a background job; omitting it follows the agent’s declared mode.
• outputSchema: Invocation-specific JSON Schema. Overrides the selected agent and parent-session schemas.

• schemaMode: "permissive" (default) accepts a retry-exhausted invalid result with a warning; "strict" fails it.

• isolated: Run in a dedicated worktree; successful changes are automatically applied to the parent checkout.

• isolated: Run in a dedicated worktree; changes are retained as patch or branch artifacts without modifying the parent checkout.

Communication

Subagents start blank — no conversation history. Parent-to-subagent IRC delivered immediately as steering. Pass large payloads via local://<path> URIs, NEVER inline text.

Format Contracts

context format:

Goal ← what the batch accomplishes

Constraints ← rules and session decisions

Contract ← shared interfaces

task format:

Target ← exact files and symbols; explicit non-goals

Change ← step-by-step add/remove/rename; APIs and patterns

Acceptance ← observable result; no project-wide commands

Available Agents

Agent spawning is currently disabled.

Pick the most specific agent; use default worker only when no specialist fits.

(READ-ONLY) (BLOCKING: inline result)

Use ONLY for investigation; do edits yourself or assign to a writing agent.