Ao Op
/install ao-op
AO Op
Use Agent Orchestrator as an external local CLI. Do not treat it as an OpenClaw plugin.
Current environment status
As of the latest verification on this Mac:
- AO source repo exists at
/Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator - Source entrypoint works:
node packages/ao/bin/ao.js --help - Global
aocommand exists, butao doctorreports:launcher entrypoint is missing - Therefore prefer the source wrapper in this skill for stable execution
Default invocation pattern
Use the wrapper script:
/Users/ShiXin/.openclaw/skills/ao-op/scripts/ao.sh \x3Cargs...>
It runs:
cd /Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator
node packages/ao/bin/ao.js \x3Cargs...>
When to use AO
Prefer AO for:
- orchestrating multiple coding-agent sessions
- managing AO dashboard / start / stop flows
- session operations such as
status,session,send,review-check - checking AO environment health with
doctor - updating the AO source installation with
update
Do not use AO when a direct OpenClaw built-in feature already solves the request more simply.
Common commands
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.
Known caveats
ao doctorcurrently reports no config file yet in the AO repo; that is expected until AO is initialized for a target projectao statuscurrently falls back to session discovery and shows no tmux sessions; that means nothing is running yet, not that AO is broken- Prefer the source wrapper over global
aountil launcher-entrypoint warning is resolved - The AO repo currently has untracked files such as
package-lock.jsonandpackages/web/dist-server/; avoid destructive cleanup unless the user asks
Maintenance
Project path standard:
- GitHub source projects should be cloned under
/Users/ShiXin/Documents/Workspace/github-project
Current AO source path:
/Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator
Update from source with:
cd /Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator
git pull --ff-only
pnpm install
pnpm -r build
Resources
scripts/ao.sh— stable wrapper for invoking AO from the source checkoutreferences/commands.md— common AO command cookbook and routing notes
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ao-op - After installation, invoke the skill by name or use
/ao-op - Provide required inputs per the skill's parameter spec and get structured output
What is Ao Op?
Use the locally installed source version of Agent Orchestrator (AO) at `/Users/ShiXin/Documents/Workspace/github-project/agent-orchestrator` through OpenClaw... It is an AI Agent Skill for Claude Code / OpenClaw, with 37 downloads so far.
How do I install Ao Op?
Run "/install ao-op" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Ao Op free?
Yes, Ao Op is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Ao Op support?
Ao Op is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Ao Op?
It is built and maintained by Kevin Stone (@chaoyang78); the current version is v1.0.0.