Skip to content

Results from this documentation version only.

    ← Alcubi Delegator

    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.

    Terminal window
    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.

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

    Terminal window
    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.

    Delegator does not keep a list of models. The agent gives the list over ACP. dg agents models and the check in dg config set default_model show the IDs that the agent gives, without change. To see the list, run:

    Terminal window
    dg agents models claude

    An adapter can bundle its own copy of the agent. The Claude adapter, claude-agent-acp, does not use the claude CLI on your PATH. It includes a copy of Claude Code through the Claude Agent SDK. Its model list is as old as the adapter. An update of the claude CLI does not change the list.

    The bundled copy also resolves aliases. If you set default_model to an alias such as sonnet, an old adapter can run an older model than the same alias gives in the agent’s own CLI.

    The list is shorter than the picker in the agent’s own CLI, even when the adapter is current. The adapter gives aliases and not the full catalogue.

    If the list does not show a model that the agent’s own CLI offers, update the adapter.

    1. See what the agent offers now:

      Terminal window
      dg agents models claude
    2. See which version of the adapter is installed:

      Terminal window
      npm ls -g @agentclientprotocol/claude-agent-acp
    3. Upgrade the adapter:

      Terminal window
      npm install -g @agentclientprotocol/claude-agent-acp@latest
    4. Run the first command again. Make sure that the new models are in the list.

    5. If the ID of your model changed, set the default again:

      Terminal window
      dg config set default_model MODEL

    Delegator does not need a restart or an upgrade. Each probe starts the adapter again, so the new list shows at once.

    For other agents:

    • Codex also runs through an adapter, @agentclientprotocol/codex-acp. Use the same npm commands with this package name.
    • An agent that speaks ACP itself does not have an adapter. Update the agent to update its list.

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

    Terminal window
    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:

    Terminal window
    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.

    The RESUME column describes whether Delegator has a command to reopen a recorded session in your terminal. When supported, dg ticket 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.

    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 agents models, dg ticket chat.