Orchestrator.incDocs

Agent adapters

The agent harnesses built into Orchestrator, with terminal and structured Chat capabilities.

View on GitHub

Most agents require a local installation and sign-in. Unreal Agent is built into Orchestrator for macOS and Linux and is Chat-only. For an installed agent, check that Orchestrator can find it and start a session:

ao agent ls --refresh
ao spawn --project my-app --name task --agent codex

Orchestrator uses the agent CLI and authentication you already installed for external harnesses. It does not bundle external provider credentials or install external adapters from npm.

Shipped agent harnesses

The current daemon registers the following capabilities. Availability still depends on platform, installed version, credentials, and permissions; a registered adapter is not proof that it is ready on your machine.

HarnessTerminal UIChatReviewer
claude-codeYesYesYes
codexYesYesYes
opencodeYesYesYes
opencode-v2YesYesYes
grokYes—Yes
cursorYesYesYes
qwenYesYes—
geminiYes——
copilotYes—Yes
kimiYesYesYes
museYes—Yes
droidYesYesYes
ampYes—Yes
agyYes—Yes
crushYes—Yes
aiderYes—Yes
gooseYes——
auggieYes—Yes
continueYes——
devinYes—Yes
ompYesYes—
hermesYesYes—
clineYes—Yes
kiroYes—Yes
kilocodeYes—Yes
vibeYes——
piYesYesYes
kimchiYesYesYes
prime-agentYes——
autohandYes—Yes
fxYes——
unreal-agentNoYes—
mimo-codeYes——
deepseek-harnessYesYes—
openhandsYes——
command-codeYesYes—

The table shows shipped capabilities, not whether an agent is ready on your machine. Run the catalog for current readiness or when scripting:

ao agent ls --refresh
ao agent ls --refresh --json

The readiness probe reports whether a harness is supported, installed, and authenticated. Spawn still performs authoritative validation.

fx (experimental)

Install fx from Settings → Harness on macOS or Linux (expected at ~/.local/bin/fx; on Windows use WSL), then spawn it in Terminal UI mode. fx Chat is not supported.

ao spawn --name fx-task --agent fx --mode tui

Chat versus Terminal UI

Unreal Agent is Chat-only; the other worker adapters provide a terminal interface. These harnesses have structured Chat drivers:

HarnessChat transport
codexCodex native app-server
claude-codeclaude-agent-acp using the user's Claude executable
opencodeNative ACP (OpenCode 1)
opencode-v2Native ACP (OpenCode 2)
droidNative ACP
kimiNative ACP
kimchiNative ACP
piSeparately installed ACP adapter; explicit bypass permissions required
cursorNative ACP
ompNative ACP
qwenNative ACP
hermesNative ACP (hermes acp)
unreal-agentBuilt into Orchestrator
deepseek-harnessNative ACP (dsh --profile acp)
command-codeNative ACP (cmd acp)

Every other harness is Terminal UI-only. Choose the initial interface with ao spawn --mode chat|tui. Compatible Claude Code and Codex sessions can hand off between Chat and Terminal UI while retaining the Orchestrator session and worktree.

Qwen Chat needs version 0.16 or newer; OMP Chat needs version 15 or newer. MiMo Code needs version 0.1.14 or newer and is Terminal UI-only, as is Gemini. Unreal Agent is built into Orchestrator for macOS/Linux, is Chat-only, and requires bypass permissions because it has no interactive approval flow. DeepSeek Chat uses dsh --profile acp. Check readiness and the provider options offered by your installed Orchestrator version before launching.

Chat registration does not imply interface handoff support. Use the switch action and its disabled reason in the session UI. Experimental reviewer modes and prompts do not sandbox tools or network access.

Choosing and configuring a harness

ao spawn --project my-app --name auth-fix --agent claude-code --mode chat

To make Codex the default worker, use ao project set-config my-app --worker-agent codex. It changes only the worker agent and keeps the rest of the project config.

--agent and --harness are aliases. Use ao project set-config --help for supported fields.

On this page