Skip to main content
Archductor is the fastest way into the suite. This gets you from nothing to an agent working on its own branch.
1

Install the desktop app

On Linux, the APT and DNF repositories install both the CLI package and the Electron desktop package:
For a manual download, pick the archductor-desktop-* artifact for your platform from the releases page.If you only want the command line, Homebrew/Linuxbrew and the lowercase archductor-* artifacts install the CLI and daemon without the UI:
APT/DNF setup, AppImage, AUR, Nix, Windows preview, and source builds are covered in Install.
2

Authenticate the tools it drives

Archductor shells out to your existing local CLIs. It does not store or proxy credentials.
Codex, Claude Code, and Gemini CLI use whatever local authentication you already have. archductor setup reports which are ready.
3

Add a repository

From the Projects page, point Archductor at an existing repository folder or clone a Git URL. One project wraps one repository.
4

Write the setup script before your first workspace

A fresh worktree has no gitignored files — so no dependencies, no .env. Two keys fix that for every workspace you will ever create:
.archductor/settings.toml
$ARCHDUCTOR_PORT is a stable per-workspace port, so parallel workspaces do not fight over 3000.
5

Create a workspace

From a branch, a prompt, a GitHub issue, a GitHub pull request, or a Linear issue. The workspace gets its own Git worktree, branch, .context directory, and reserved port block.
One workspace is one branch is one reviewable unit. If two changes should be reviewed separately, give them separate workspaces.
6

Start an agent and review

Start a Shell, Codex, Claude Code, or Gemini session inside the workspace. When it settles, review the changed files, diffs, todos, and comments in the app, then create or merge the pull request and archive the workspace.

​
Where to go next

Your first workspace

The same path with the reasoning, and what to do when it breaks.

Running work in parallel

Ports, copied files, conflicts, layouts, shortcuts.

Project setup

Scripts, prompts, checks, and merge rules in .archductor/settings.toml.

Running on a server

Host the daemon headless and drive it from anywhere.