Skip to content
Agent Orchestration
Command

/project

Manage projects: register repos, inspect, configure per-project settings, and remove.

From plugin
agent-orchestrator
14k20 skills20 commands
$ npx -y skills add OrchestratorInc/agent-orchestrator --agent claude-code

Command definition

project.md

ao project

Manage projects: register repos, inspect, configure per-project settings, and remove.

Syntax

ao project <subcommand> [args] [flags]

Subcommands

---

ao project add

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; Orchestrator 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"

---

ao project ls

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

---

ao project get

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

---

ao project rm

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

---

ao project set-config

Update a project's saved configuration. Orchestrator reads these settings when it spawns a session. Flags change only the fields they name and keep the rest of the saved config; a repeatable flag replaces that whole list or map. `--config-json` replaces the full object, and `--clear` removes all configuration.

**Warning:** `--config-json` replaces the whole config. The CLI silently ignores unknown keys in it, so a typo can leave the replacement empty. 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) | - | | `--pre-remove stringArray` | Command to run before workspace removal (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`, `orchestrator.agentConfig.mode`, and `effort` under any `agentConfig`. 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=development" --post-create "npm install"

``

Read more
@orchestratorinc
Ships withagent-orchestrator

Plan, run and supervise fleets of agents from task to merged PR. Desktop (macOS, Windows, Linux) + iPhone & Android apps. Supports Claude Code, Codex & 35+ coding agents.

Stars on GitHub

Momentum

stars in total
14.4k
Star history of OrchestratorInc/agent-orchestrator on GitHub, a chart by star-history.com

Other commands on agent-orchestrator.

cua

cua

Command

Drive native desktop apps (read the screen, click, type) through [Cua Driver](https://cua.ai). The user installs Cua Driver and…

cue

cue

Command

Create and inspect reusable Cues for a local Orchestrator project. Both orchestrators and workers can use this command from their…

More commands from other plugins.

COMMAND_COMPLIANCE_REPORT

COMMAND_COMPLIANCE_REP…

Command

Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools…

@ruvnet@ruvnetInstall Command
ask

ask

Command

This compatibility command keeps `/oh-my-claudecode:ask` available without loading the full `ask` skill description in every…

@yeachan-heo@yeachan-heoInstall Command
code-review

code-review

Command

Technical code review for quality, bugs, and AGENTS.md compliance

archon10d24k
@coleam00@coleam00Install Command