Migration

npm is frozen and no longer recommended

npm still works, but it is no longer the recommended way to install AO. 0.10.0 is the final version published to npm, and the @aoagents/ao package is frozen and will not receive further updates. Move to the desktop app, which auto-updates and owns the daemon. Existing CLI users can run ao start to fetch and open the desktop build; the npm ao command stays available as that one-time bridge.

From @composio/agent-orchestrator to @aoagents/ao

The npm scope moved to @aoagents/ao. If you installed under the old name:

npm uninstall -g @composio/agent-orchestrator
npm install -g @aoagents/ao

Your config and data directory (~/.agent-orchestrator) don't change — no data migration needed. Use the current GitHub repo URL (AgentWrapper/agent-orchestrator) for docs, releases, and issue links.

ao spawn <project> <issue> → ao spawn <issue>

The old two-argument form is rejected with an error. Pick the project via -p or by running from inside its worktree:

# old
ao spawn myproject 42

# new
ao spawn 42 -p myproject
# or, from inside the project's worktree:
ao spawn 42

ao init → ao start

ao init has been removed. Use ao start instead; it auto-creates agent-orchestrator.yaml on first run and opens the dashboard in one step.

Upgrading

Preferred:

ao update

The command detects your install method (npm-global, pnpm-global, git, or unknown) and picks the right upgrade path. Override behaviour with --skip-smoke or --smoke-only for git installs.

Before major upgrades

1. ao status — see what's running.
2. ao session cleanup — archive finished sessions.
3. ao stop --all — halt every AO instance.
4. Upgrade.
5. ao doctor on the new version.