Installation · Plexus Docs

To install Plexus, download the native desktop build for your platform — macOS, Linux, or Windows — and install it like any other app; it keeps itself up to date after that.

Download for Windows

The button picks the right build for your OS automatically; use the platform menu on it to choose another. Prefer to pick by hand? Every asset is listed below.

Download

Every installer lives on the public releases page:

text

https://github.com/CodedWords/plexus-releases/releases

Open the latest release and grab the asset that matches your platform from the sections below. Filenames carry the version (shown here as <version>, e.g. 0.1.0).

macOS

Plexus publishes separate builds for Apple Silicon and Intel — pick the one that matches your Mac.

Mac	Download
Apple Silicon (M1 and later)	`Plexus_<version>_aarch64.dmg`
Intel	`Plexus_<version>_x64.dmg`

Open the .dmg, drag Plexus into Applications, then launch it from there.

Linux

Linux builds are x86_64 (amd64) only, in two formats. The .deb suits Debian/Ubuntu-based distros; the .AppImage is a portable single-file binary that runs anywhere.

Format	Download
Debian/Ubuntu package	`Plexus_<version>_amd64.deb`
Portable AppImage	`Plexus_<version>_amd64.AppImage`

Install the .deb:

bash

sudo apt install ./Plexus_<version>_amd64.deb

Or run the AppImage directly:

bash

chmod +x Plexus_<version>_amd64.AppImage
./Plexus_<version>_amd64.AppImage

Windows

Windows builds are x64 only.

Format	Download
Installer	`Plexus_<version>_x64-setup.exe`

Run the -setup.exe and follow the prompts. It installs for the current user, so you don't need administrator rights, and Plexus is added to the Start menu when it finishes.

Note

An .msi is also published on the releases page, for per-machine and managed deployments. Both formats keep themselves up to date with a matching package, so an existing .msi install needs no action — it upgrades in place, asking for administrator approval each time, because that's what a per-machine install requires. If you do reinstall it by hand, take the .msi from the releases page: the download button on this site always hands out the -setup.exe, which is a different, per-user install rather than an upgrade of the one you have. If you'd rather switch to the per-user installer, that's exactly what to run — but Windows asks once to remove the MSI version first, and you should accept that prompt. Declining it doesn't stop the new install, it just leaves the old registration behind, and Windows then asks the same question on every future update. If that already happened, Plexus offers to clear it up — see Staying up to date.

Verify prerequisites

Plexus drives the Claude Code CLI and Git, so both must be installed and on your PATH. After installing, confirm them from a terminal:

bash

claude --help
git --version

If claude isn't found, Requirements explains how Plexus locates it and the Path to the Claude program override. For pull-request features you connect a git provider (GitHub or Bitbucket) inside the app — no extra CLI to install. See Connections.

Staying up to date

Plexus updates itself — you don't need to revisit the releases page for future versions.

It checks for a new release on launch and every ~30 minutes while it's open.
When one is available, you get a one-click Install & restart, or Install when idle — which applies the update automatically once all your sessions finish, so a running agent is never interrupted. It waits for a short countdown (which you can cancel) before restarting.
You can also check on demand from Settings → About → Check for updates.
You're prompted once per new version — no repeated nagging.
Every update is signature-verified before it's applied, so a tampered build won't install.
Updates arrive in the format you installed — an .msi install updates with an .msi, the -setup.exe with a -setup.exe.
After an update, a What's new window shows what changed the first time you run the new version — once per version, with the release's changes listed down the left-hand side, one per feature. If you skipped several releases, they're all selectable at the top of the window; if you're coming from a version older than the window itself, you get the notes for the release you landed on and the rest are on the Changelog page. A brand-new install opens straight into Plexus instead. You can reopen the window any time from Settings → About → What's new.

The same release notes are published on the Changelog page, newest first — handy for reading what's coming before you update, or catching up on a release you clicked past.

Note

Windows: "An older Plexus installation is still registered"? Earlier versions could update an .msi install onto the -setup.exe one, leaving the older per-machine install registered behind — which is what makes Windows ask "Are you sure you want to uninstall this product?" during an update. If Plexus finds that leftover it offers to remove it: choose Remove it and confirm the Windows permission prompt. That uninstalls the old per-machine copy (the one under C:\Program Files\Plexus, along with its Start-menu shortcut) and the question stops for good. The Plexus you're running is a different, per-user install and stays exactly where it is, and your settings, projects and sessions aren't stored in either install folder — they're untouched. If Windows takes longer than expected to finish, Plexus offers Check again instead of asking you to repeat the removal. The offer also lives in Settings → About until it's done.

Installed? Head to Getting started to add a repository and run your first session.