Skip to main content
Adapters are the bridge between AoA’s orchestration layer and agent runtimes. Each adapter knows how to invoke a specific type of AI agent and capture its results.

How Adapters Work

When a heartbeat fires, AoA:
  1. Looks up the agent’s adapterType and adapterConfig
  2. Calls the adapter’s execute() function with the execution context
  3. The adapter spawns or calls the agent runtime
  4. The adapter captures stdout, parses usage/cost data, and returns a structured result

Built-in Adapters

Adapter Architecture

Each adapter is a package with three modules:
Three registries consume these modules:

Choosing an Adapter

  • Need a coding agent on the local machine? Use claude_local, codex_local, opencode_local, cursor, gemini_local, or hermes_local
  • Need to run a script or command? Use process
  • Need to call an HTTP endpoint or external service? Use http
  • Need to run a remote OpenClaw agent? Use openclaw
  • Need something custom? See creating-an-adapter.md