Skip to content

Installation

Download and install the Pipemason CLI on your machine.

The Pipemason CLI is a single, code-signed and notarized binary. There is no Node, npm, or runtime to install alongside it — the runner ships everything it needs in one executable. Builds are published for macOS (Apple Silicon and Intel), Linux (x64 and arm64), and Windows (x64).

Note

You need a Pipemason account before the CLI is useful. Sign up at pipemason.com and start the 14-day free trial first, then come back here to install.

Homebrew (macOS / Linux)

The recommended install path on Apple Silicon Macs and Linux is Homebrew. On an Intel Mac, current Homebrew may refuse to install; use the single-use install script instead. It installs the same signed and notarized Intel (x64) build.

brew trust crashbytes/tap
brew install crashbytes/tap/pipemason

Homebrew puts pipemason on your PATH automatically. To upgrade, always run brew update && brew upgrade pipemason — the brew update refreshes the tap so brew can actually see new releases. A bare brew upgrade pipemason only knows the versions your local tap clone has already synced, and Homebrew refreshes that clone at most once a day; because pipemason often ships several releases in a day, a bare upgrade can report you're already current when a newer version is out.

Heads-up

Homebrew 6.0+ requires a one-time trust step. As of Homebrew 6.0 (June 2026), third-party taps must be explicitly trusted on each machine before brew will load them — a tap cannot mark itself trusted. Without it you'll see Refusing to load formula … from untrusted tap, and brew upgrade silently won't see new versions. If you installed before upgrading to Homebrew 6.0, run brew trust crashbytes/tap once, then brew update && brew upgrade pipemason.

Scoop (Windows)

On Windows, install with Scoop. Add the bucket once, then install:

scoop bucket add crashbytes https://github.com/CrashBytes/scoop-bucket
scoop install pipemason

Future releases upgrade with scoop update pipemason.

Single-use install script

On Intel Macs, CI runners and locked-down boxes where you cannot use a package manager, use the single-use install command shown on the onboarding page. Open pipemason.com/onboarding and copy the command verbatim — it embeds a token scoped to your account and plan:

curl -fsSL https://api.pipemason.com/install/<your-token> | bash

The script detects your platform, downloads the matching binary, and drops it at ~/.local/bin/pipemason. If ~/.local/bin is not already on your PATH, the script reminds you to add it.

Heads-up

The install token is single-use and expires 15 minutes after the onboarding page renders. If it expires before you run it, reload /onboarding and a fresh token mints automatically.

Verify the install

Confirm the binary is installed and on your path:

pipemason --version

command not found

If your shell reports pipemason: command not found after the script install, the install directory is not on your PATH. Add ~/.local/bin to your shell profile and reopen the terminal:

export PATH="$HOME/.local/bin:$PATH"

Supported platforms

The runner ships as a signed binary for these targets:

  • macOS — Apple Silicon (arm64) and Intel (x64)
  • Linux — x64 and arm64
  • Windows — x64

Next step

With the CLI installed, pair it to your account so it can register runs and stream them to your dashboard. Continue to Pairing the runner.