Install

Download

Installers for every supported platform are on the latest release.

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.

Unsigned, and it does not update itself

Nothing is code-signed, so the first launch raises an unknown-publisher warning on every OS — SmartScreen on Windows, Gatekeeper on macOS. There is also no auto-update: a newer version means downloading it yourself.

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/ai-pos.git
cd ai-pos
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 AI-POS 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 AI-POS looks for it first. The portable zip carries it too, beside ai-pos.exe.

You do not need to set up PATH manually either. When AI-POS 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 aipos-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 aipos-mcp