automation
Manage durable recurring session automations through the daemon API.
Manage projects: register repos, inspect, configure per-project settings, and remove.
$ npx -y skills add OrchestratorInc/agent-orchestrator --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/projectContext preview
What this command does when you run it.
Manage projects: register repos, inspect, configure per-project settings, and remove.
Manage projects: register repos, inspect, configure per-project settings, and remove.
ao project <subcommand> [args] [flags]
---
Register a local git repo as a project so sessions can be spawned in it. The path must be an existing git repository on disk. With `--as-workspace`, the path may be a parent folder containing direct child git repositories; AO initializes/adopts the parent as the root repo and gitignores children.
**Syntax:**
ao project add [flags]
**Flags:**
| Flag | Meaning | Default / Required | |---|---|---| | `--as-workspace` | Register a parent folder as a workspace project (root-as-repo plus direct child repos) | - | | `--id string` | Project id | Derived by the daemon from the path | | `--name string` | Display name | - | | `--orchestrator-agent string` | Default orchestrator session agent | - | | `--path string` | Absolute path to the local git repo | Required | | `--worker-agent string` | Default worker session agent | - |
**Examples:**
# Register a repo as a project ao project add --path /path/to/agent-orchestrator --name "agent-orchestrator"
# Register a workspace (parent folder containing multiple repos) ao project add --path /path/to/side-quests --as-workspace --name "side-quests"
---
List registered projects. Aliases: `ls`, `list`.
**Syntax:**
ao project ls [flags]
**Flags:**
| Flag | Meaning | Default / Required | |---|---|---| | `--json` | Output projects as JSON | - |
**Examples:**
# List all registered projects ao project ls
---
Fetch one registered project.
**Syntax:**
ao project get <id> [flags]
**Flags:**
| Flag | Meaning | Default / Required | |---|---|---| | `--json` | Output project as JSON | - |
**Examples:**
# Get details for the agent-orchestrator project ao project get agent-orchestrator
---
Remove a registered project. Aliases: `rm`, `remove`, `delete`.
**Syntax:**
ao project rm <id> [flags]
**Flags:**
| Flag | Meaning | Default / Required | |---|---|---| | `--json` | Output removal result as JSON | - | | `-y, --yes` | Skip confirmation prompt | - |
**Examples:**
# Remove a project (with confirmation) ao project rm agent-orchestrator
# Remove without prompt ao project rm agent-orchestrator -y
---
Replace a project's saved configuration. AO reads these settings when it spawns a session. Use flags for common fields or `--config-json` for the full object. `--clear` removes all configuration.
**Warning:** This command replaces the whole config, even when you use focused flags. The CLI silently ignores unknown keys in `--config-json`, so a typo can leave the replacement empty. Its config mirror also omits `effort`; `ao project get --json` cannot show it, and a CLI configuration replacement drops existing effort values. Use Project Settings in the desktop app or the daemon API when you need to preserve or change effort. See the [full-config warning](https://docs.orchestrator.inc/configuration/projects/#update-from-the-cli) before updating project settings from the CLI.
**Syntax:**
ao project set-config <id> [flags]
**Flags:**
| Flag | Meaning | Default / Required | |---|---|---| | `--agent-rules string` | Project-specific standing instructions appended to worker session prompts | - | | `--agent-rules-file string` | Repo-relative file containing project-specific worker standing instructions | - | | `--canonical-repo-url string` | Explicit upstream HTTPS repository URL used for PR claims (same provider, host, and port as `origin`) | - | | `--clear` | Clear all config | - | | `--config-json string` | Full config as a JSON object (overrides field flags) | - | | `--default-branch string` | Base branch new session worktrees are created from | - | | `--env stringArray` | Env var `KEY=VALUE` forwarded into sessions (repeatable) | - | | `--json` | Output the updated project as JSON | - | | `--model string` | Agent model override (e.g. `claude-opus-4-5`) | - | | `--orchestrator-agent string` | Harness override for orchestrator sessions | - | | `--orchestrator-rules string` | Project-specific standing instructions appended to orchestrator session prompts | - | | `--permission string` | Permission mode: `default`, `accept-edits`, `auto`, `bypass-permissions` | - | | `--post-create stringArray` | Command to run after workspace creation (repeatable) | - | | `--session-prefix string` | Displayed session-id prefix | - | | `--symlink stringArray` | Repo-relative path to symlink into workspaces (repeatable) | - | | `--tracker-assignee string` | Issue assignee required for tracker intake eligibility | - | | `--tracker-intake` | Opt this project into GitHub or GitLab issue intake; inert unless the daemon also has `AO_TRACKER_INTAKE=on` | Disabled | | `--tracker-repo string` | Provider-native issue repository (`owner/repo` or `group/subgroup/repo`); defaults to the Git origin | - | | `--reviewer stringArray` | Reviewer harness for worker PRs (repeatable) | - | | `--worker-agent string` | Harness override for worker sessions | - |
Use `--config-json` for fields without a dedicated flag, including `trackerIntake.provider`, `autoReview`, `containerReap.disabled`, `agentConfig.mode`, `worker.agentConfig.mode`, and `orchestrator.agentConfig.mode`. The full-config replacement warning above still applies.
**Examples:**
# Set default branch and model for a project ao project set-config agent-orchestrator --default-branch main --model claude-opus-4-5
# Replace the complete config; include every setting you want to keep
ao project set-config agent-orchestrator --config-json \
'{"defaultBranch":"main","agentConfig":{"model":"claude-opus-4-5"}}'# Set an env var and a post-create command ao project set-config agent-orchestrator --env "NODE_ENV=developm
Run and supervise teams of coding agents from planning to merge. Any harness (Claude code, codex, +25 more). Desktop, web, mobile, and cloud agents.
Manage durable recurring session automations through the daemon API.
Inspect and control the current AO session's target-isolated browser. The desktop app must be…
Create and inspect reusable Cues for a local AO project. Both orchestrators and workers can…
Run local AO health checks. Use this to diagnose setup problems or verify the environment is…
Import reads the legacy Agent Orchestrator flat-file store (`~/.agent-orchestrator`)…
Manage orchestrator sessions.