Install

Linux is the primary validated target. Windows is a preview target. Check Requirements before installing.

Which artifact do you want?

Releases ship two families of artifact with similar names. Picking the wrong one is the most common first-run problem.

You want	Artifact	Contains
The desktop app	`archductor-desktop-<version>-x86_64.AppImage`, `archductor-desktop_<version>_amd64.deb`, `archductor-desktop-<version>.x86_64.rpm`, `.dmg`, or the Windows installer	The Electron UI plus bundled `archcar` and `archductor` sidecars
CLI and daemon only	`archductor-<version>-x86_64.AppImage`, `archductor-<version>-linux-x86_64.tar.gz`, Homebrew/Linuxbrew, AUR, or Nix	`archductor` and `archcar`, no UI

archductor-desktop is the GUI. Lowercase archductor is the command line.

archductor with no subcommand prints help. It does not open a window — the GUI is a separate executable that the desktop installers place in your application menu.

The desktop installers are self-contained: they bundle Chromium, Node, and both Rust sidecars, so the target machine needs no Archductor-specific runtime libraries. Only git, gh, and your agent CLIs have to exist on the host.

Desktop app

On Linux, use the Perceo-owned APT or DNF repository when possible. Install both packages: archductor provides the CLI and daemon, and archductor-desktop provides the Electron app.

curl -fsSLo /tmp/archductor-archive-keyring.gpg \
  https://www.perceo.ai/apt/archductor-archive-keyring.gpg
sudo install -Dm644 /tmp/archductor-archive-keyring.gpg \
  /usr/share/keyrings/archductor-archive-keyring.gpg
sudo curl -fsSLo /etc/apt/sources.list.d/archductor.sources \
  https://www.perceo.ai/apt/archductor.sources
sudo apt update
sudo apt install archductor archductor-desktop

sudo curl -fsSLo /etc/yum.repos.d/archductor.repo \
  https://www.perceo.ai/rpm/archductor.repo
sudo dnf makecache --repo archductor
sudo dnf install archductor archductor-desktop

VERSION=0.8.3
curl -Lo archductor-desktop.AppImage \
  https://github.com/perceo-ai/conductor-arch/releases/download/v${VERSION}/archductor-desktop-${VERSION}-x86_64.AppImage
chmod +x archductor-desktop.AppImage
sudo mv archductor-desktop.AppImage /usr/local/bin/archductor-desktop
archductor-desktop

For macOS, Windows preview builds, or manual Linux downloads, use the releases page and pick the archductor-desktop-* artifact for your platform.

CLI and daemon

VERSION=0.8.3
curl -Lo archductor.AppImage \
  https://github.com/perceo-ai/conductor-arch/releases/download/v${VERSION}/archductor-${VERSION}-x86_64.AppImage
chmod +x archductor.AppImage
sudo mv archductor.AppImage /usr/local/bin/archductor
archductor doctor

brew tap perceo-ai/tap
brew install archductor

paru -S archductor

nix run github:perceo-ai/conductor-arch#archductor -- doctor

If you install binaries by hand, copy archcar next to archductor. The CLI resolves the daemon as a sibling of its own executable before falling back to PATH, so a lone archductor in /usr/local/bin cannot start a daemon. The CLI AppImage and package-manager CLI packages place both for you. They do not install the Electron desktop app unless the command also installs archductor-desktop.

Flatpak packaging uses app ID ai.perceo.Archductor and remains experimental until the sandbox passes Flathub review — arbitrary repository access needs broad filesystem permissions.

Build from source

Install Git, GitHub CLI, SQLite, OpenSSH, pkg-config, and Rust, then:

git clone https://github.com/perceo-ai/conductor-arch
cd conductor-arch
cargo build --workspace --release --locked
./target/release/archductor doctor

make targets:

make build            # dev build of the Rust workspace
make build-release    # release build (--locked)
make check            # fmt + clippy + tests
make cli              # run the CLI in branch-scoped dev mode
make archcar          # run the archcar sidecar in branch-scoped dev mode

The Electron app is built and run separately:

make desktop-install         # pnpm install
make desktop-dev             # run the UI in dev mode (auto-spawns archcar)
make desktop-package-linux   # build sidecars + Linux installers

make cli, make archcar, and make desktop-dev are branch-scoped: they set separate XDG config, data, state, and cache directories per branch, so several checkouts can run side by side while you dogfood. make dev-env prints the active paths.

Windows preview

Tagged releases build archductor-<version>-windows-x86_64.zip containing the CLI and the archcar sidecar.

winget install --id Git.Git --id GitHub.cli

Source builds use the MSYS2 UCRT64 toolchain and the x86_64-pc-windows-gnu target; the CI workflow is the canonical recipe. Windows compiles and packages, but its runtime checklist has not passed — treat it as preview.

Verify the download

Release artifacts ship with checksum manifests. CLI artifacts are listed in SHA256SUMS; Linux desktop packages are listed in SHA256SUMS-desktop-linux.txt. The public package repositories are signed with fingerprint 55C0 EB36 2097 45CE D529 18FF 929C EA68 D5E8 E8D0.

sha256sum -c SHA256SUMS
gh release view --repo perceo-ai/conductor-arch --web

Verify provenance or attestations too when a release includes them.

Your first workspace

Authenticate the tools, add a repository, get to a merged pull request.

Running on a server

Install the daemon headless and drive it from your laptop.

Get started

Guides

Reference

Which artifact do you want?

Desktop app

CLI and daemon

Build from source

Windows preview

Verify the download

Next

Your first workspace

Running on a server

​Which artifact do you want?

​Desktop app

​CLI and daemon

​Build from source

​Windows preview

​Verify the download

​Next

Your first workspace

Running on a server

Which artifact do you want?

Desktop app

CLI and daemon

Build from source

Windows preview

Verify the download

Next