Install

Download

Installers for every supported platform are on the releases page.

Platform	What to take
Windows x64	.msi or .exe to install — or the _portable.zip, which unzips and runs with no installer at all
macOS arm64	.dmg — the release also carries an .app.tar.gz of the same build, which you do not need
Linux x64	.deb, .AppImage, or .rpm

The portable Windows build exists for machines where installing is the thing that gets blocked. It carries the same two executables the installer places, and a README.txt explaining what it can and cannot get past.

The release also lists .sig files and a latest.json. Those are for the in-app updater (below), not for you to download.

Unsigned

Nothing carries a publisher certificate and nothing is notarized, so every OS stops the first launch — SmartScreen on Windows, Gatekeeper on macOS. Neither is a dead end: reference/building has the click path past each one. macOS bundles do carry an ad-hoc signature, which names no publisher and is what keeps Gatekeeper’s refusal recoverable rather than a flat “the application is damaged”.

Take the newest release. Older ones are kept for reference, not for use: the ad-hoc signature arrived partway through, and a build from before it does not open on macOS at all — no “Open Anyway”, no way past it.

Updating

From 0.2.0 on, an installed copy updates itself when you ask it to: Settings → About → Check for updates, then Download and install. The download is verified against a signature before anything is replaced, and the app restarts on the new version. Nothing is checked or downloaded in the background — it happens when you press the button and not otherwise.

• Running terminal sessions end when the app restarts; if any are running, you are asked first. Their tabs come back afterwards.
• On Windows, close agents in external terminals first. An agent CLI connected to a workspace keeps the hub (nextup-mcp.exe) open, and Windows will not replace a file that is in use. The app checks for this after downloading and waits for you rather than starting an install that would fail halfway.
• The portable zip does not update itself — its installer would put a second, installed copy beside it. Download the new zip and unzip it over the old folder.
• 0.1.3 and earlier have no update button. Install 0.2.0 once by hand; from there on the button is there.

Once it is installed, the first screen is the Projects list. The app tour starts there, and your first project walks the wizard.

Build from source

Building stays fully supported, and is what you want if you are developing or on a platform the release does not cover.

Prerequisites (Windows)

Requirement	Notes
Git	The build starts with git clone; any recent version
Rust (stable, MSVC toolchain)	If the C++ build tools are missing, the rustup installer offers to set them up for you through the Visual Studio installer — accept that, or install the “Desktop development with C++” workload yourself first
pnpm	You don’t need to manage your Node version — the repo pins it and pnpm downloads it automatically
WebView2	Built into Windows 11; Windows 10 needs it installed separately

macOS and Linux

CI builds Linux x64 and macOS arm64 as well; the table above is Windows-specific but the build commands are the same. Prerequisites on those platforms are the standard Tauri v2 ones (the Tauri prerequisites guide lists them — a set of system libraries on Linux, Xcode Command Line Tools on macOS).

Build

git clone https://github.com/white1024/agent-nextup.git
cd agent-nextup
pnpm install        # frontend dependencies
pnpm tauri build    # produces an installer (the first build takes a while)

The installer lands under target/release/bundle/ (.msi or .exe) — run it to install, then launch Agent NextUp from the Start menu. If you are developing, pnpm tauri dev runs the app without installing.

A build of your own is unsigned for the same reason the released ones are, and raises the same first-launch warning. The difference is that you compiled it, so approve it the way you would any other local build.

The hub server (for AI agents)

Nothing to do. The hub server an AI agent talks to (see Connect an AI agent) is compiled as part of the build — in CI for a released installer, by pnpm tauri build for one of your own — and ships inside it, landing next to the app executable where Agent NextUp looks for it first. The portable zip carries it too, beside agent-nextup.exe.

You do not need to set up PATH manually either. When Agent NextUp initialises a workspace it points that workspace’s .mcp.json at the absolute path of that executable. If the pointer ever goes stale — you moved the app, or you are running from a source tree — open the Tools page and press Repair connection on the nextup-mcp health card to re-point it. If that card reports the executable missing entirely, it tells you the one command that rebuilds it (run it in the cloned repo):

cargo build --release -p nextup-mcp