Multi-agent collaboration
Collaboration turns one objective into inspectable participants, task dependencies, approvals, and budgets. Start with the guided entry point; use the command reference when you need precise control over participants, dependencies, or the run lifecycle.
If the CLI has not completed its first-run initialization, follow Quickstart to run Claude Code or Codex first, then return here for multi-agent collaboration. Collaboration remains subject to the separate device, model, and approval boundaries described in Devices and security, Models and routing, and Approval policies.
Recommended entry point
originrouter collaborate
Start the guided collaboration flow. The interactive flow collects the objective, participants, and permissions.
By default, the CLI shows the generated Team/configuration and then waits again for the Planner's plan. You do not need --review; it is retained for compatibility and is equivalent to the default behavior.
For automation that deliberately accepts both startup gates, use:
originrouter collaborate "Prepare the release and verify the result independently" --yes
--yes accepts only the Team/configuration and plan startup confirmations. It does not bypass subsequent action approvals, and cannot be combined with --review.
Start from Agent Workspace
originrouter --mode plan-build-verify "Implement the payment callback and add regression tests"
To start a build-and-review flow from the Claude workspace, use:
originrouter -c claude --mode build-review "Implement the settings-page change"
auto selects the smallest effective structure. Prefer plan-build-verify for production-sensitive changes and review-panel for comparing proposals.
Inspect and control a Run
originrouter collaboration list
originrouter collaboration show <run-id>
originrouter collaboration attach <run-id>
originrouter collaboration attention <run-id>
originrouter collaboration doctor <run-id>
list: list visible Runs.show: inspect a Run's state and summary.attach: follow a Run's output continuously.attention: list pending confirmations or blocking items.doctor: diagnose a Run's execution state.
Control commands include confirm, revise, pause, resume, retry, cancel, archive, delete, and export. Export any result that still needs to be retained before deletion.
Drafts and automation
originrouter collaboration drafts
originrouter collaboration draft show <draft-id>
originrouter collaboration create --draft <draft-id>
originrouter collaboration export <run-id> --format markdown
drafts: list available Drafts.draft show: inspect Draft content and validation results.create --draft: create a Run from a Draft.export: export Run results.
For scripted result processing, use supported --json output rather than parsing colored user-facing terminal text.