Skip to content

Job pack · supervisor

Multi-agent team

A second agent is a context boundary. Supervisor, crew+flows, or handoff. Never unsupervised group chat on prod tools.

When: Specialists need different tools or a fresh window, and a parent must synthesize.

Roles must change tools or schema. Fresh windows. Structured returns. Bound the talk. Prefer supervisor or handoff over group chat.

GET /api/canon/jobs/multi-agent-crew?format=md

Matching skill · Multi-agent topologies

Playbooks

Doctrine to load

Refuse

  • Shared mega-context. A crew sharing one bloated window. Specialists drown in each other's work.
  • Role-play without a different ACI. Backstories that do not change tools, prompt constraints, or schema. Theater.
  • Unsupervised group chat. Agents talking to each other against production tools with no turn bound and no typed messages.
  • Handoff history dump. Transfer of control copies the entire conversation into the specialist.

Checklists

Ready to build

  • Named termination: done schema, max turns, token/money cap.
  • Sandbox / allowlist for every side effect. Secrets in the executor.
  • An explicit context builder: pinned, working, recalled, compacted.
  • A golden set of 20–50 real tasks, run in CI on prompt change.
  • Launch / pause / resume APIs. HITL is a tool that checkpoints.

Harness quality

  • Filesystem workspace. Disk is source of truth; the window is a cache.
  • Progressive-disclosure skill loader.
  • Plan/act modes. Plan is a file the human can edit.
  • Subagent spawner with reduced tools and a written return.
  • Sandbox plus permission gates.
  • Verifier in the loop (test, typecheck, build, browser).

Recipes

Default corpus

langgraphcrewaiopenai-agentsdeepagents