Install and connect an agent

Install dg, then connect the coding agent that will run your tickets.

Before you begin

You need Git, an existing Git repository with at least one commit, and an installed, authenticated coding agent.

Install the CLI

macOS / Linux

Run this in your terminal:

curl -fsSL https://alcubi.ai/delegator/install.sh | sh

If you use Windows Subsystem for Linux (WSL), a Linux environment inside Windows, run this command in your Linux terminal too.

Windows (PowerShell)

Run this in your current Windows PowerShell 5.1 or PowerShell 7 session:

iwr -useb https://alcubi.ai/delegator/install.ps1 | iex

For custom versions, installation directories, unattended installs, or upgrades, see the Windows installation guide.

Both installers download and verify the latest stable release, then start guided setup in an interactive terminal. After installation, check the version:

dg version

If your terminal cannot find dg, see troubleshooting.

Run guided setup

If either installer already completed guided setup, you can skip dg init here. Otherwise, start it now. The commands in this section work in PowerShell and macOS/Linux shells:

dg init

Review your configuration:

dg config

Setup discovers agents and asks which one should run new tickets. It can offer to install the Claude or Codex adapter using npm; that setup path also requires Node.js and npm. Authentication and provider access must be configured for your chosen agent.

Setup also asks whether to enable optional telemetry. Yes is selected, but no choice is stored and nothing is sent until you submit the prompt. Cancelling or leaving setup first keeps the setting at null, which sends nothing. For scripted setup, submit the choice explicitly with dg init --telemetry=true or dg init --telemetry=false; omitting the flag preserves an existing choice and leaves a new instance unanswered.

See optional telemetry for the data sent, reporting schedule, privacy limits, and config controls.

Connect Claude or Codex with ACP

Delegator uses the Agent Client Protocol (ACP) to communicate with coding agents. For Claude Code and Codex, you need an ACP adapter in addition to the agent’s usual command-line installation. Having claude or codex on your PATH does not mean its adapter is installed.

The guided setup can offer to install the appropriate adapter for you. This requires Node.js and npm. If you prefer to install it yourself, run the command for the agent you want to use:

Claude Code

npm install -g @agentclientprotocol/claude-agent-acp

This adds the claude-agent-acp command that Delegator uses to run Claude tickets.

Codex

npm install -g @agentclientprotocol/codex-acp

This adds the codex-acp command that Delegator uses to run Codex tickets.

Install only the adapters you plan to use. An adapter does not replace authentication: make sure your chosen agent is installed, signed in, and ready to use. After installing an adapter manually, run dg init to select it as your default agent.

Discover your agents

dg agents --all

The registry shows known commands, executable paths, resume support, and the default agent. A missing entry means its executable is not on PATH. For Claude and Codex, check that the corresponding ACP adapter command is available.

Choose a small first run

Agents run with your user permissions, and unattended ACP tool requests are approved. Start in a repository you are comfortable letting the agent modify. Keep the first task small enough to inspect completely.

Next, create and review your first ticket. For custom executable paths and adapters, see choose and configure agents.

Reference: dg init, dg agents, dg config.