ap-adapters

ap-adapters

When to use

• Before spawning: which adapters are actually installed and what each can do on this host.
• A spawn fails or bills oddly — is the credential there? Which providers can it reach?
• You need to install a new agent CLI (claude-code, hermes, aider, …) as an adapter.

Inspect what is installed

adapter_list({})
// → [{ "slug": "claude-code", "version": "0.1.0", "protocol": "acp", ... },
//    { "slug": "hermes", ... }]

role_list({})
// → spawn-time roles: 'executor' (leaf, cannot delegate), 'supervisor' (may spawn children)

adapter_list is the static manifest view. For what an adapter can actually DO here, ask harness_capabilities:

harness_capabilities({ "adapter": "claude-code" })
// → { "authStores": [...],            // where creds live (env vars, keychain files)
//     "providers": [ { "id": "anthropic", "cred": { "present": true, ... } } ],
//     "models": { "mechanism": "free-form", "ids": [...] },
//     "application": { "modelApply": "config", "postureApply": "none" } }

harness_capabilities is ground truth — it complements the manifest with the live/parsed picture from each adapter's own native config/creds store. Omit adapter to get every installed one.

Install

adapter_install({ "slug": "claude-code" })

Ordinary install failures come back as ok: false in a normal result — read the message, don't assume success. A fresh install still needs credentials before it can bill: run auth_discover_credentials and auth_profile_import (see ap-models-auth).

CLI equivalents

agentproto adapters list            # = adapter_list
agentproto adapters show <slug>
agentproto adapters install <slug>  # = adapter_install
agentproto adapters uninstall <slug>
agentproto adapters enable/disable <slug>
agentproto install <slug>           # shorthand install
agentproto setup <slug>             # interactive credential/config setup
agentproto run <slug>               # run the adapter directly
agentproto chat <adapter>           # interactive chat with a specific adapter