Built-in capabilities
Agent, runtime, workspace, tracker, SCM, notification, and terminal support compiled into Orchestrator.
To use a built-in capability, choose an agent or project type in Orchestrator. Capabilities ship with the desktop app; they are not npm plugins and cannot be installed through a marketplace. For an external agent, install its CLI, sign in, then run ao agent ls --refresh to check readiness. Unreal Agent is built into Orchestrator for Chat on supported macOS and Linux.
Capability map
| Area | Shipped support | Selection |
|---|---|---|
| Agents | Worker, Chat, and reviewer adapters with separate capability sets | Per project or session |
| Runtime | Native PTY hosts on macOS/Linux, legacy/fallback tmux, ConPTY on Windows | Automatic by platform |
| Workspace | Git worktrees, Scratch, and standalone directories | Automatic by project kind |
| Tracker | GitHub and GitLab issue intake | Per-project opt-in, plus AO_TRACKER_INTAKE on the daemon |
| SCM | GitHub/GitLab PR or MR, checks, reviews, and mergeability | Derived from the Git repository |
| Notifications | Durable history, desktop toasts, and paired-device mobile push | Built in |
| Terminal | Desktop xterm surface over Orchestrator's terminal mux | Built in |
Agents are the configurable adapter set
Use ao agent ls --refresh to see the exact daemon-advertised catalog and whether each local CLI is installed and authenticated. ao spawn --agent <name> selects a harness for one session; project worker and orchestrator defaults are stored in typed project configuration.
The other areas are daemon-owned boundaries, not interchangeable marketplace slots. In particular, the runtime is selected for the operating system, Git repositories use worktrees, and Scratch projects use Orchestrator-managed directories.
Legacy agent-orchestrator.yaml plugin, notifier, runtime, workspace, tracker, and SCM blocks are not active configuration in the rewrite. ao import reports unsupported legacy fields as dropped.