Use Agent Orchestrator as an external local CLI. Do not treat it as an OpenClaw plugin.
As of the latest verification on this Mac:
/Users/ShiXin/Documents/Workspace/github-project/agent-orchestratornode packages/ao/bin/ao.js --helpao command exists, but ao doctor reports: launcher entrypoint is missingUse the wrapper script:
/Users/ShiXin/.openclaw/skills/ao-op/scripts/ao.sh <args...>
It runs:
cd /Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator
node packages/ao/bin/ao.js <args...>
Prefer AO for:
status, session, send, review-checkdoctorupdateDo not use AO when a direct OpenClaw built-in feature already solves the request more simply.
Read references/commands.md for examples.
Safe/common commands:
ao.sh --help
ao.sh doctor
ao.sh status
ao.sh config-help
ao.sh review-check
ao.sh update
Project-specific commands usually need to run inside a target repo or require AO config.
ao doctor currently reports no config file yet in the AO repo; that is expected until AO is initialized for a target projectao status currently falls back to session discovery and shows no tmux sessions; that means nothing is running yet, not that AO is brokenao until launcher-entrypoint warning is resolvedpackage-lock.json and packages/web/dist-server/; avoid destructive cleanup unless the user asksProject path standard:
/Users/ShiXin/Documents/Workspace/github-projectCurrent AO source path:
/Users/ShiXin/Documents/Workspace/github-project/agent-orchestratorUpdate from source with:
cd /Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator
git pull --ff-only
pnpm install
pnpm -r build
scripts/ao.sh — stable wrapper for invoking AO from the source checkoutreferences/commands.md — common AO command cookbook and routing notes共 1 个版本