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 Archductor

On Linux, the AppImage is the shortest path:
Or use a package manager:
Other channels — AUR, Nix, Windows preview, 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 and Claude Code use whatever local authentication you already have.
3

Launch the app

With no arguments the AppImage opens the GTK app. With arguments it forwards to the command-line interface.
4

Add a project

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

Create a workspace

Create a workspace from a branch, a prompt, a GitHub issue, a GitHub PR, or a Linear issue. The workspace gets its own Git worktree, branch, .context directory, and a stable ARCHDUCTOR_PORT range.
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, or Claude Code session inside the workspace. When it settles, review the changed files, diffs, todos, and comments in the app, then create or merge the PR and archive the workspace.

​
Where to go next

Core workflow

Projects, workspaces, branches, and sessions — and how they nest.

Project setup

Shared scripts, prompts, and workspace defaults in .archductor/settings.toml.

Archivum

Stand up the knowledge layer with the guided installer.

Archfleet

Run computer-use agents on isolated VMs.