Skip to main content
Archductor drives tools you already have. It does not bundle or proxy them, and it does not store credentials. Run gh auth login before using any pull-request feature. Agent CLIs use your existing local authentication. LINEAR_API_KEY is required for Linear-sourced workspace creation.
Agent CLIs are optional. Archductor is useful with Shell sessions alone if what you want is isolated worktree workspaces and a review surface.

​
Which agents actually run as sessions

archductor archcar providers prints what your build knows and how completely it drives each one. archductor setup prints what is installed and authenticated on this machine.

​
Platform

  • Linux — the primary manually validated target. APT and DNF repositories publish both CLI and desktop packages; Homebrew/Linuxbrew publishes the CLI/headless package. CI covers glibc, musl, Debian, and Fedora.
  • macOS — compiles and smoke-tests; the desktop installer builds a .dmg.
  • Windows — preview. Compiles and packages, but its runtime checklist has not passed.
  • WSL — supported as a Linux environment. Not a substitute for a native Windows build.
Desktop installers and the archductor-desktop APT/DNF packages bundle Chromium, Node, and both Rust sidecars, so the host needs no Archductor-specific runtime libraries. Source builds need Rust and the usual build toolchain — see Install.

​
Running headless

None of this requires a display. The archcar daemon has no GUI dependency, so a headless server can host it while your laptop drives it — see Running on a server. Agent CLIs and gh authentication have to live on whichever machine runs the daemon.