> ## Documentation Index
> Fetch the complete documentation index at: https://docs.perceo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Desktop control plane for running coding agents across isolated Git worktree workspaces.

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.

<Info>
  Inspired by [Conductor](https://conductor.build). Archductor targets Linux
  desktops and native Windows with GTK4/libadwaita. Linux is the primary validated
  target; Windows is a preview target.
</Info>

<CardGroup cols={2}>
  <Card title="Install" icon="download" href="/archductor/install">
    AppImage, Homebrew, AUR, Nix, Windows preview, or source.
  </Card>

  <Card title="Core workflow" icon="git-branch" href="/archductor/workflow">
    Projects, repositories, workspaces, branches, and sessions.
  </Card>

  <Card title="Project setup" icon="sliders-horizontal" href="/archductor/project-setup">
    Shared scripts, prompts, and defaults in `.archductor/settings.toml`.
  </Card>

  <Card title="Requirements" icon="list-checks" href="/archductor/requirements">
    What has to be installed and authenticated first.
  </Card>
</CardGroup>

## Product structure

Archductor uses these terms consistently. They nest.

| Term                | What it means                                                                                                     | Relationship                          |
| ------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
| Project             | The Archductor entry for one codebase. Holds repository settings, scripts, instructions, and the workspace list.  | 1 project contains 1 repository       |
| Repository          | The Git codebase behind a project, from a local folder, Git URL, or quick-start flow.                             | 1 repository contains many workspaces |
| Workspace           | An isolated copy of the repository for one task, issue, experiment, or PR.                                        | 1 workspace maps to 1 branch          |
| Branch              | The Git branch checked out inside a workspace. Usually the review and PR unit.                                    | 1 branch has 1 working tree           |
| Working tree        | The files on disk for one workspace, created with Git worktrees.                                                  | 1 working tree belongs to 1 workspace |
| Running environment | The app, server, watchers, tests, terminals, and agent processes inside a workspace.                              | 1 workspace can run many processes    |
| Turn                | The actions an agent takes between one user message and the next in the same thread. One tool call is not a turn. | 1 turn contains many tool calls       |

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](/archivum/overview).
It is not the behavior verification layer either — that is
[Archfleet](/archfleet/overview).

Archductor owns the workspace lifecycle and everything that happens between
"start this task" and "the PR is merged."