🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more
Sign In

@aoagents/ao

Package Overview
Dependencies
Maintainers
1
Versions
29
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@aoagents/ao

Orchestrate parallel AI coding agents — global CLI wrapper

npmnpm
Version
0.9.4
Version published
Maintainers
1
Created
Source

Agent Orchestrator (ao)

The orchestration layer for parallel AI coding agents.

npm version License: MIT GitHub stars Discord

Agent Orchestrator

Spawn parallel AI coding agents, each in its own git worktree, on a single machine. Agents autonomously fix CI failures, address review comments, and open PRs — you supervise the whole fleet from one dashboard.

Agent-agnostic (Claude Code, Codex, Aider, Cursor, OpenCode) · Runtime-agnostic (tmux, ConPTY/process, Docker) · Tracker-agnostic (GitHub, Linear, GitLab)

Install

npm install -g @aoagents/ao

Nightly builds (latest main): npm install -g @aoagents/ao@nightly — back to stable with @latest.

Prerequisites: Node.js 20.18.3+, Git 2.25+, the gh CLI, and at least one coding-agent CLI (e.g. Claude Code).

  • macOS / Linux: tmuxbrew install tmux or sudo apt install tmux.
  • Windows: PowerShell 7+ recommended; tmux is not required (AO uses native ConPTY via the process runtime).

Quick start

Point it at any repo — it clones, configures, and launches the dashboard in one command:

ao start https://github.com/your-org/your-repo

Or from inside an existing local repo:

cd ~/your-project && ao start

The dashboard opens at http://localhost:3000 and an orchestrator agent starts managing your project. Add more repos any time:

ao start ~/path/to/another-repo

You don't need to learn the CLI — the dashboard and the orchestrator agent drive everything. (Individual ao commands are documented in the CLI Reference and used internally by the orchestrator.)

How it works

  • You startao start launches the dashboard and an orchestrator agent.
  • Orchestrator spawns workers — each issue gets its own agent in an isolated git worktree and branch.
  • Agents work autonomously — they read code, write tests, and open PRs.
  • Reactions handle feedback — CI failures and review comments are routed back to the responsible agent automatically.
  • You review and merge — you're pulled in only when human judgment is needed.

Pluggable by design

Seven plugin slots; the lifecycle state machine stays in core:

SlotDefaultAlternatives
Runtimetmux (macOS/Linux) / process (Windows)process, docker
Agentclaude-codecodex, aider, cursor, opencode, kimicode
Workspaceworktreeclone
Trackergithublinear, gitlab
SCMgithubgitlab
Notifierdesktopslack, discord, composio, webhook, openclaw
Terminaliterm2web

Why Agent Orchestrator?

Running one AI agent in a terminal is easy. Running 30 across different issues, branches, and PRs is a coordination problem: creating branches, detecting stuck agents, reading CI failures, forwarding review comments, tracking which PRs are ready, and cleaning up afterward.

Agent Orchestrator handles the isolation, feedback routing, and status tracking. You ao start and walk away — then review PRs and make decisions. The rest is automated.

Documentation

License

MIT © ComposioHQ

Keywords

ai

FAQs

Package last updated on 02 Jun 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts