Download

Get Probe

Two downloads in every release: the command-line tool that reviews code changes, and the desktop application that watches office documents. Pick the one that matches your work, or both.

CLI archives contain the executable, LICENSE, NOTICE and README.md in a folder named after the version and platform. Probe Desktop is a single .exe on Windows and a zipped Probe Desktop.app on macOS.

Release history

Loading releases from GitHub…

Verify a download

Every release publishes a SHA256SUMS file covering the CLI archives and the Probe Desktop files. Download it next to the file, then check its digest:

# Linux
grep probe-v0.5.1-linux-amd64.tar.gz SHA256SUMS | sha256sum --check
# macOS
grep probe-desktop-v0.5.1-darwin-universal.zip SHA256SUMS | shasum -a 256 --check
# Windows (PowerShell): compare with the matching line of SHA256SUMS
Get-FileHash .\probe-desktop-v0.5.1-windows-amd64.exe -Algorithm SHA256

Checksums detect corrupted or mismatched files. The downloads are not signed or notarized yet, so the systems warn on first launch:

  • Windows: SmartScreen may show "Windows protected your PC" for Probe Desktop. Choose More info, then Run anyway.
  • macOS: a copy downloaded with a browser is quarantined. For Probe Desktop, right-click Probe Desktop.app and choose Open, or run xattr -dr com.apple.quarantine "Probe Desktop.app"; for the CLI, xattr -d com.apple.quarantine probe.

Build from source

With Go and Git, from a checkout. The CLI needs Go 1.23 or newer:

git clone https://github.com/gvinsot/Probe.git
cd Probe/app
go build -o probe ./cmd/probe
# or build every platform archive with checksums into dist/
go run ./tools/build -version dev -targets windows/amd64,linux/amd64,darwin/arm64

Probe Desktop needs Go 1.26 or newer; the macOS application must be built on a Mac:

cd Probe/desktop
# Windows executable, from any system
GOWORK=off GOOS=windows CGO_ENABLED=0 go build -ldflags "-H=windowsgui" ./cmd/probe-desktop
# macOS application (on a Mac)
bash scripts/build-macos.sh dev

Release process and CI artifacts are described in RELEASE.md and desktop/README.md.