get started

Quickstart

Five commands from a fresh install to your first shipped feature. The runner is a signed single binary — no Node toolchain required.

1. Install the runner

On macOS / Linux:

brew install crashbytes/tap/pipemason

On Windows (PowerShell):

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

Or — handy on CI runners and locked-down boxes — generate a single-use install command from the onboarding page:

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

2. Pair the runner to your account

pipemason login

The runner prints a 9-character code and opens pipemason.com/pair. Enter the code there to bind the runner to your account. You only do this once per machine.

3. Initialise a target repo

Pipemason detects your domains (web / api / mobile / db / cloud) from package.json, Podfile, and friends, then scaffolds .pipeline/ with a pre-filled config.yml.

cd ~/your-repo
pipemason init
git add .pipeline/ && git commit -m "init pipemason workspace"

4. Set your Anthropic key

Pipemason is BYO Anthropic — the runner reads the key from your shell and never sends it to our servers.

export ANTHROPIC_API_KEY=sk-ant-...

5. Start a run

pipemason start "ABC-1234 add passkey login"

Watch the live monitor at pipemason.com/dashboard as the pipeline runs. When it finishes you have a tested branch with atomic commits, ready to review.

What lives where

• .pipeline/config.yml — repo-level config (domains, commands, model tiering, gates).
• .pipeline/STATE.md — current run state.
• .pipeline/spec.md — frozen spec from your input.
• .pipeline/contracts/ — frozen interfaces between domains.
• .pipeline/iterations.log — append-only audit trail.

Next steps

• Want to ship a whole system, not just one feature? See Programs.
• Want to understand what each phase does? See Phases.
• Need a command you don't see here? See the CLI reference.