Agents

An agent is the upstream coding tool you're talking to: claude-code, codex, opencode, or your own. Profiles spawn agents — see Profiles for the much more interesting half of this.

Registering an agent

[[agents]]
id = "claude-code"                 # how profiles reference it
provider = "acp-claude-code"       # which vendor adapter to use
model = "claude-sonnet-4-5"        # default model for instances of this agent

[agents.env]
ANTHROPIC_API_KEY = "${env:ANTHROPIC_API_KEY}"

${env:VAR} interpolates from your shell environment at daemon start.

Supported providers

Provider	Vendor
acp-claude-code	Anthropic Claude via @zed-industries/claude-code-acp.
acp-codex	OpenAI Codex via @zed-industries/codex-acp.
acp-opencode	opencode.
acp-custom	Any binary that speaks the Agent Client Protocol — supply your own command + args.

Custom command

By default each provider knows how to spawn its own vendor — you don't need to specify command / args. Override only when you need a non-default invocation:

[[agents]]
id = "claude-code-canary"
provider = "acp-claude-code"
command = "bunx"
args = ["--bun", "@zed-industries/claude-code-acp@canary"]

Custom ACP agents

Bring any binary that speaks ACP:

[[agents]]
id = "my-agent"
provider = "acp-custom"
command = "/usr/local/bin/my-agent"
args = ["--acp"]

[agents.env]
MY_AGENT_TOKEN = "${env:MY_AGENT_TOKEN}"

Choosing the default

[agent]
default = "claude-code"

[profile]
default = "ask"

[agent] default falls back when nothing else picks an agent (a profile didn't specify one, no [[profiles]] matched). [profile] default is the profile new instances open with.

Both must reference real ids — the daemon refuses to start with a typo.