Windows installation options

For a normal installation, follow the quick installation guide. This guide covers custom settings and repeat installations in PowerShell.

Requirements and defaults

Use 64-bit Windows (x86-64/amd64 or ARM64), Windows PowerShell 5.1 or PowerShell 7, and HTTPS access to GitHub. Run installer commands in PowerShell, not Command Prompt (cmd.exe). No Unix utilities, administrator privileges, or permanent execution-policy change are required.

With no options or environment overrides, the installer downloads the latest stable release for your architecture, verifies its SHA-256 checksum, and installs dg.exe in %LOCALAPPDATA%\Programs\Delegator\bin.

Options and environment overrides

The short iwr | iex command uses environment defaults. To pass explicit parameters, use the ScriptBlock invocation in your current PowerShell session instead. This tested form selects a version, uses a directory containing spaces, and skips guided setup. Replace the example version v1.2.3 with a published release containing Windows binaries:

& ([scriptblock]::Create((Invoke-WebRequest -UseBasicParsing -Uri 'https://alcubi.ai/delegator/install.ps1').Content)) -Version v1.2.3 -InstallDir "$env:LOCALAPPDATA\Delegator Tools" -NonInteractive

Parameter	Environment default	Behavior
-Version	DG_VERSION	Select a release; latest stable if unset. Accepts an optional leading v, prerelease suffix, and build metadata.
-InstallDir	DG_INSTALL_DIR	Choose the directory containing dg.exe; defaults to %LOCALAPPDATA%\Programs\Delegator\bin. Quote paths containing spaces; semicolons are rejected because the directory goes on PATH.
-NonInteractive	DG_NON_INTERACTIVE	Skip guided setup for unattended installation. Environment value 1 skips setup; 0 allows it when the console is interactive. Other nonempty values are rejected.
-Help	None	Print installer help without installing or starting setup.

Explicit parameters override their corresponding environment variables. -NonInteractive:$false overrides DG_NON_INTERACTIVE=1, but setup still requires an interactive console. Non-interactive installation does not configure an agent: run dg init later, or select an available agent explicitly with dg init --agent codex. Older releases with alcubi-delegator_ asset filenames are supported when they contain Windows binaries and the canonical checksum file.

To fetch the script and display help:

& ([scriptblock]::Create((Invoke-WebRequest -UseBasicParsing -Uri 'https://alcubi.ai/delegator/install.ps1').Content)) -Help

This command downloads the script itself. -Help does not query release metadata, download release archives, change PATH, or run setup. With a saved script, ./install.ps1 -Help needs no network access. -Version selects the CLI binary release; the bootstrap still fetches the installer from the latest stable release.

Upgrade or reinstall

Close running dg processes, then rerun the installation command. Without a version override it upgrades to the latest stable release; select the same version to reinstall. Reuse your custom -InstallDir or DG_INSTALL_DIR when updating that installation. Existing PATH entries are preserved without adding the same directory again. Use -NonInteractive to skip setup on repeat installations.

The installer downloads and verifies the archive before replacing dg.exe, and keeps a backup until user PATH persistence succeeds. Download, checksum, replacement, or PATH persistence failures preserve the previous binary. If rollback itself fails, the error identifies the backup to recover. See Windows installation or upgrade failed for recovery steps.

Guided setup and unattended installation

In an interactive console, the installer starts dg init in the same terminal. Use -NonInteractive or set DG_NON_INTERACTIVE to 1 to skip setup. Non-interactive hosts and redirected console streams also skip setup and print the command to run later.

Cancellation or setup failure leaves the CLI installed and usable. Run dg init explicitly when ready to retry. Setup requires Git and an installed, authenticated coding agent; see connect an agent.

PATH and command discovery

The installer adds its directory to your user PATH and the current PowerShell session’s PATH, preserving existing entries and leaving the system PATH unchanged. Run the command in your current session: a child powershell.exe or pwsh process cannot update its parent’s PATH.

Check which command PowerShell finds:

Get-Command dg

Then check the installed version:

dg version

Newly opened terminals should pick up the user PATH. If another terminal cannot find dg, close and reopen the terminal application. If it still cannot find the command or finds an older copy, see command discovery troubleshooting.

Using Linux on Windows

Windows Subsystem for Linux (WSL) runs a Linux environment inside Windows. Use the macOS/Linux command inside your WSL distribution, with Git and your agent installed there. Native Windows and WSL are separate installation environments; choose the command for the environment where you will run tickets.