Choose and configure agents

Delegator starts coding agents through the Agent Client Protocol (ACP). Some agents expose ACP directly; others use a separate adapter. The registry tells Delegator which executable and arguments to use.

Inspect the registry

dg agents
dg agents --all

The first command shows available registered executables. --all also includes missing ones and their installation hints. The output shows the command, resolved path, terminal resume support, and current default.

Built-in entries cover Claude, Codex, Gemini, Goose, OpenCode, GitHub Copilot, Cursor Agent, and Pi. An entry is configuration, not a support guarantee: agent versions, authentication, and provider settings affect whether a run succeeds.

Select the default

For guided first-time setup, use dg init. To change an existing instance to an available agent:

dg config set default_agent codex
dg config get default_agent

The setting applies to new runs. Continuing an existing session depends on the agent and session recorded for that ticket.

Set an executable path

If a known adapter is installed outside PATH, point the registry at its executable:

dg agents add codex --path /opt/bin/codex-acp

Use the actual executable path on your machine. The path must exist and be executable.

For a custom ACP command:

dg agents add local --command /opt/bin/local-agent --arg serve --arg=--acp
dg config set default_agent local

This example registers an executable with arguments serve --acp; replace both with the interface your agent actually supports. --command registers a custom command, while --path updates a known entry. They cannot be combined.

Know what resume support means

The RESUME column describes whether Delegator has a command to reopen a recorded session in your terminal. When supported, dg chat ID starts that command in the ticket worktree.

A custom command does not automatically gain terminal resume support. The existence of an ACP command also does not prove an agent supports every session operation. Try a small ticket before relying on a new agent for a larger workflow.

Plan for permissions and usage

Agent processes inherit the environment of dg and run with your user permissions. Unattended ACP requests are approved. Keep credentials and external systems in mind when deciding where to run an agent.

Delegator records aggregate token counts when the agent reports them. Missing usage is not evidence that a run was free; Delegator does not calculate provider bills or enforce a token-spending ceiling.

Reference: dg agents, dg agents add, dg chat.