Installation

Download

Linux — signed, auto-updating (see Updates). Grab the .AppImage or .deb from the latest release (asset filenames are versioned, e.g. magpie_0.1.0_amd64.AppImage, so there's no evergreen direct-download link to give here):

• .AppImage — self-updates in place through the app; no install step, just run it.
• .deb — installs system-wide via dpkg/apt, but does not self-update (see Updates) — reinstall a new .deb by hand for each release.

macOS — not published yet. Code signing and notarization aren't wired up (see Architecture); build from source below in the meantime, or watch ROADMAP.md for when a signed .dmg and Homebrew cask land.

Verify

Every release includes SHA256SUMS and a build provenance attestation:

gh release download vX.Y.Z --repo akshaykrishh/magpie
sha256sum -c SHA256SUMS
gh attestation verify magpie_X.Y.Z_amd64.AppImage --repo akshaykrishh/magpie

See SECURITY.md for what each check does and doesn't prove, and how the update signing key itself is protected.

Build from source

Requires Rust (stable) and pnpm. macOS builds also require Xcode Command Line Tools.

git clone https://github.com/akshaykrishh/magpie.git
cd magpie/apps/desktop
pnpm install
pnpm tauri dev

pnpm tauri dev compiles the Rust core and launches the app with hot reload on the frontend. For a release build (produces a .dmg on macOS, or a .deb/.AppImage on Linux):

pnpm tauri build

The bundle lands in target/release/bundle/ at the repo root -- this is a Cargo workspace, so every crate (including the desktop app) shares one target/ directory rather than a per-app one.

Development builds

Every push to main builds and bundles the app on both macOS and Ubuntu runners. Unsigned artifacts (.dmg, .deb, .AppImage) are attached to each workflow run -- useful for trying an unreleased commit without a Rust toolchain. Two things to know before using one:

• These builds don't self-update through the in-app updater — they're not part of the signed release pipeline at all, so you'd need to grab a new one by hand each time.
• On macOS specifically, rebuilding and reinstalling one of these revokes your Accessibility grant on every rebuild (see Architecture's Signing section) — one-key capture will silently stop working until you re-grant it. This is a real cost of using an unsigned build, not a hypothetical one.

The CLI

The CLI (magpie) and MCP server binary both build from the same workspace:

cargo build --release -p magpie-cli
# binary at target/release/magpie

See CLI reference for every subcommand, and MCP integration for wiring magpie serve-mcp into Claude Code or Cursor.