Skip to main content
Archductor is a desktop control plane for running coding agents across isolated Git worktree workspaces. Use it when one codebase has several streams of work in flight: create a workspace, start Codex or Claude Code, review the diff, open or merge a GitHub pull request, archive the workspace, then start the next task without leaving the app.
Inspired by Conductor. Archductor targets Linux desktops and native Windows with GTK4/libadwaita. Linux is the primary validated target; Windows is a preview target.

Install

AppImage, Homebrew, AUR, Nix, Windows preview, or source.

Core workflow

Projects, repositories, workspaces, branches, and sessions.

Project setup

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

Requirements

What has to be installed and authenticated first.

​
Product structure

Archductor uses these terms consistently. They nest. The practical rule:
  • Projects own repository-level defaults and configuration.
  • Workspaces are the task unit.
  • Sessions, terminals, setup and run scripts, and agents are part of the running environment inside a workspace.

​
What works today

The app supports the core loop, with some rough edges.
  • Add a project from an existing repository path, or clone a Git URL from the Projects page.
  • Create workspaces from a branch, prompt, GitHub issue, GitHub PR, or Linear issue.
  • Give each workspace its own Git worktree, branch, .context directory, and stable ARCHDUCTOR_PORT range.
  • Run multiple workspaces for the same repository in parallel.
  • Start multiple Shell, Codex, or Claude Code sessions inside one workspace.
  • Use an embedded workspace terminal, setup/run/stop controls, logs, and process lists.
  • Review changed files, file diffs, todos, local review comments, sibling workspace conflicts, PR checks, and GitHub PR comments.
  • Stage review comments, failing checks, or PR comments into the selected agent session.
  • Create, refresh, merge, and archive GitHub PRs through local gh auth.
  • Restore archived workspaces and inspect saved session history.

​
What it does not own

Archductor is not the long-term memory system — that is Archivum. It is not the behavior verification layer either — that is Archfleet. Archductor owns the workspace lifecycle and everything that happens between “start this task” and “the PR is merged.”