orchestration
使用Orca编排实现结构化的多智能体协调:线程化消息、阻塞式询问/回复流程、任务分发、worker_done/升级等待、任务DAG、决策门、协调器循环,或在智能体间分解工作。当用户未明确要求监督、监控、等待结果或协调时,对于表述为“hand off”、“handoff”、“handover”、“give this to another agent
npx skills add https://github.com/stablyai/orca --skill orchestrationOrca Orchestration
This discovery stub loads the version-matched guide from the Orca executable used for this session.
Never substitute a non-Orca subagent tool when the user asked for Orca orchestration.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
ORCA_CLI_COMMANDenvironment variable is set, use its value. Orca exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT, useorca-dev. - Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide. Never run bareorcathere — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine. - Otherwise, use
orca.
Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run ORCA literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.
Load the version-matched guide before running Orca commands
ORCA skills get orchestration
That prints the compact, version-matched guide for the exact binary that will handle your
next commands. It covers the normal local coordinator loop and dispatched-worker
obligations. For a conditional action gate such as remote placement, uncertain release
recovery, or expanded DAG work, load only the reference that gate names with
ORCA skills get orchestration --reference references/<file>.md
(--references lists the names). If that binary rejects --reference, run
ORCA skills get orchestration --full and read the named bundled reference before acting.
Use the selected executable's --help for commands or flags the guide does not cover. A
runtime_unavailable error is usually transient while Orca is busy or restarting: wait a few
seconds and retry the command. Before retrying a command that changes something, check whether
it already took effect, and reuse any request ID the error names. ORCA open can bring Orca's
window to the front over the user's work, so never run it to retry a failed command. Run it only
when the user asks, or when Orca is really not running: ORCA status --json reports
result.app.running: false, or every command, ORCA status included, still cannot connect
after about 30 seconds of retries. If a command fails with runtime_access_denied, your
sandbox blocked the connection: re-run it with escalated permissions, and do not run
ORCA open or restart Orca. If skills get is unknown,
explain that updating Orca restores the guide; use --help for read-only discovery and do not
guess unsupported commands.