AO's current Go backend uses built-in adapters and services. These capabilities ship with the desktop app; they are not npm plugins and cannot be installed through a marketplace.
Capability map
| Area | Shipped support | Selection |
|---|---|---|
| Agents | 24 terminal agent adapters; four also support structured Chat | Per project or session |
| Runtime | tmux on macOS/Linux; ConPTY on Windows | Automatic by platform |
| Workspace | Git worktrees and AO-managed Scratch directories | Automatic by project kind |
| Tracker | GitHub issue intake | Per-project, opt-in |
| SCM | GitHub PR, checks, reviews, and mergeability | Derived from the Git repository |
| Notifications | Durable in-app history and Electron toasts | Built in |
| Terminal | Desktop xterm surface over AO'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 AO-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.