Skip to main content
Harbor’s generic acp integration installs and runs agents from the ACP Registry inside the task environment. ACP provides a common protocol between clients and agents.
--agent acp:... selects an ACP registry agent. It is different from --bridge acp, which connects a simulated user to the target agent.

Run a registry agent

Harbor supports all acp agents in the ACP Registry Github or ACP registry.json. The four agents below are examples. Use acp:<agent_id> for the latest entry or acp:<agent_id>@<version> to pin a version.
Unlike Harbor’s installed agents, ACP agents do not receive provider credentials automatically. Pass each required variable with --agent-env (--ae).Authentication rules also vary by agent. Some agents require --agent-kwarg authenticate_method_id=... in addition to the credential. Check the agent’s documentation in the ACP Registry.
Authentication references: Codex ACP, Claude, Cursor ACP, and OpenCode.

Common options

Pass these options with --agent-kwarg (--ak) or agents[].kwargs: See the ACP agent constructor for all supported options.
Run the generic acp agent with a local agent.json file:

Output

ACP runs write acp.txt, acp-events.jsonl, acp-summary.json, and an ATIF trajectory named trajectory.json to the agent log directory.