acp

Run the ACP (Agent Client Protocol) bridge that talks to a BuilderForce Agents Gateway.

This command speaks ACP over stdio for IDEs and forwards prompts to the Gateway over WebSocket. It keeps ACP sessions mapped to Gateway session keys.

Usage

builderforce acp

# Remote Gateway
builderforce acp --url wss://gateway-host:18789 --token <token>

# Attach to an existing session key
builderforce acp --session agent:main:main

# Attach by label (must already exist)
builderforce acp --session-label "support inbox"

# Reset the session key before the first prompt
builderforce acp --session agent:main:main --reset-session

ACP client (debug)

Use the built-in ACP client to sanity-check the bridge without an IDE. It spawns the ACP bridge and lets you type prompts interactively.

builderforce acp client

# Point the spawned bridge at a remote Gateway
builderforce acp client --server-args --url wss://gateway-host:18789 --token <token>

# Override the server command (default: builderforce)
builderforce acp client --server "node" --server-args builderforce.mjs acp --url ws://127.0.0.1:19001

How to use this

Use ACP when an IDE (or other client) speaks Agent Client Protocol and you want it to drive a BuilderForce Agents Gateway session.

Ensure the Gateway is running (local or remote).
Configure the Gateway target (config or flags).
Point your IDE to run builderforce acp over stdio.

Example config (persisted):

builderforce config set gateway.remote.url wss://gateway-host:18789
builderforce config set gateway.remote.token <token>

Example direct run (no config write):

builderforce acp --url wss://gateway-host:18789 --token <token>

Selecting agents

ACP does not pick agents directly. It routes by the Gateway session key.

Use agent-scoped session keys to target a specific agent:

builderforce acp --session agent:main:main
builderforce acp --session agent:design:main
builderforce acp --session agent:qa:bug-123

Each ACP session maps to a single Gateway session key. One agent can have many sessions; ACP defaults to an isolated acp:<uuid> session unless you override the key or label.

Zed editor setup

Add a custom ACP agent in ~/.config/zed/settings.json (or use Zed’s Settings UI):

{
  "agent_servers": {
    "BuilderForce Agents ACP": {
      "type": "custom",
      "command": "builderforce",
      "args": ["acp"],
      "env": {}
    }
  }
}

To target a specific Gateway or agent:

{
  "agent_servers": {
    "BuilderForce Agents ACP": {
      "type": "custom",
      "command": "builderforce",
      "args": [
        "acp",
        "--url",
        "wss://gateway-host:18789",
        "--token",
        "<token>",
        "--session",
        "agent:design:main"
      ],
      "env": {}
    }
  }
}

In Zed, open the Agent panel and select “BuilderForce Agents ACP” to start a thread.

Session mapping

By default, ACP sessions get an isolated Gateway session key with an acp: prefix. To reuse a known session, pass a session key or label:

--session <key>: use a specific Gateway session key.
--session-label <label>: resolve an existing session by label.
--reset-session: mint a fresh session id for that key (same key, new transcript).

If your ACP client supports metadata, you can override per session:

{
  "_meta": {
    "sessionKey": "agent:main:main",
    "sessionLabel": "support inbox",
    "resetSession": true
  }
}

Learn more about session keys at /concepts/session.

Options

--url <url>: Gateway WebSocket URL (defaults to gateway.remote.url when configured).
--token <token>: Gateway auth token.
--password <password>: Gateway auth password.
--session <key>: default session key.
--session-label <label>: default session label to resolve.
--require-existing: fail if the session key/label does not exist.
--reset-session: reset the session key before first use.
--no-prefix-cwd: do not prefix prompts with the working directory.
--verbose, -v: verbose logging to stderr.

`acp client` options

--cwd <dir>: working directory for the ACP session.
--server <command>: ACP server command (default: builderforce).
--server-args <args...>: extra arguments passed to the ACP server.
--server-verbose: enable verbose logging on the ACP server.
--verbose, -v: verbose client logging.

acp

acp