docs(config): config.toml.example uses non-existent `claude --acp` flag

[lemonicefate]

Description

Not a duplicate of #418 / #447. Those address CLAUDE_CODE_EXECUTABLE
wiring inside Dockerfile.claude (which claude binary the adapter
internally invokes). This issue is about the user-facing
config.toml.example itself pointing to a CLI flag that does not exist.

Summary

The Claude Code agent block in config.toml.example (currently lines 35–40
on main) tells users to launch the Claude CLI with --acp:

# [agent]
# command = "claude"
# args = ["--acp"]
# working_dir = "/home/agent"
# env = { ANTHROPIC_API_KEY = "${ANTHROPIC_API_KEY}" }

But Claude Code's CLI has no --acp flag — invoking it fails immediately:

$ claude --acp
error: unknown option '--acp'

ACP support for Claude Code is provided by the separate npm wrapper
[@agentclientprotocol/claude-agent-acp](https://github.com/agentclientprotocol/claude
which exposes a claude-agent-acp binary. The rest of the repo already
documents this correctly:

• README.md agent table (line 118): `claude-agent-acp`
• Dockerfile.claude: npm install -g @agentclientprotocol/claude-agent-acp …
• docs/claude-code.md → "Manual config.toml" section uses
  command = "claude-agent-acp", args = []

Only config.toml.example is out of sync, so anyone uncommenting that block
on a non-Docker host hits a confusing failure that the docs and Dockerfile
do not predict.

Reproduce

# host with Node ≥ 20
npm install -g @anthropic-ai/claude-code           # Claude Code CLI
cp config.toml.example config.toml
# uncomment the [agent] / claude block as written
openab run -c config.toml
# → adapter spawn fails with: error: unknown option '--acp'

Environment

• openab: latest main
• Host: Linux, Node v22.11.0 (Node ≥ 20 required by claude-agent-acp due to JSON import attributes)
• @agentclientprotocol/claude-agent-acp v0.29.x

Suggested Change

Update the commented Claude block in config.toml.example to match
docs/claude-code.md:

# [agent]
# command = "claude-agent-acp"
# args = []
# working_dir = "/home/agent"
# # Install the adapter on the host first (requires Node >= 20):
# #   npm install -g @agentclientprotocol/claude-agent-acp
# # Auth via: `claude setup-token` (CLAUDE_CODE_OAUTH_TOKEN), or ANTHROPIC_API_KEY.
# env = { CLAUDE_CODE_OAUTH_TOKEN = "${CLAUDE_CODE_OAUTH_TOKEN}" }
# # Optional: pin which `claude` binary the adapter invokes internally (see #418, #447).
# # env = { CLAUDE_CODE_OAUTH_TOKEN = "${CLAUDE_CODE_OAUTH_TOKEN}", CLAUDE_CODE_EXECUTABLE = "/usr/local/bin/claude" }

[CHC-Agent]

Issue at a Glance

config.toml.example (L41-44)          README.md (L118)
┌──────────────────────────┐    ┌──────────────────────────┐
│ command = "claude"       │    │ claude-agent-acp         │
│ args = ["--acp"]         │    │                          │
└──────────┬───────────────┘    └──────────────────────────┘
           │                    docs/claude-code.md (L31-32)
           ▼                    ┌──────────────────────────┐
    $ claude --acp              │ command = "claude-agent-acp" │
    error: unknown option       │ args = []                │
                                └──────────────────────────┘

Hi @lemonicefate,

Confirmed — config.toml.example is the only file out of sync. The README agent table and docs/claude-code.md both correctly reference claude-agent-acp.

Related:

• Dockerfile.claude installs @anthropic-ai/claude-code but claude-agent-acp adapter never uses it #418 — CLAUDE_CODE_EXECUTABLE wiring in Dockerfile (CLOSED, different scope)
• PR fix: wire CLAUDE_CODE_EXECUTABLE so adapter uses pinned claude-code #447 by @AkashiSN — MERGED (wires CLAUDE_CODE_EXECUTABLE, different scope)

The suggested change in the issue body looks correct. PR welcome — this is a 2-line fix in config.toml.example.