Getting Started

Install

One line on Windows (PowerShell):

irm https://raw.githubusercontent.com/lacodda/rigger/main/tools/install.ps1 | iex

One line on macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/lacodda/rigger/main/tools/install.sh | sh

On Windows, use the PowerShell line

install.sh carries the macOS and Linux builds only. Running it from Git Bash, MSYS2 or Cygwin stops with a pointer to install.ps1 rather than installing anything.

Via npm:

npm i -g @lacodda/rigger

Via cargo:

cargo install rigger

Or download the archive for your platform from Releases (Windows x86_64, Linux x86_64, macOS arm64), unpack and put rigger on your PATH.

The short name

Every installer leaves rgr beside rigger: the same program, half the typing.

> rgr --version
rigger 0.9.0

It is a link, not a second copy - a hard link on Windows, a symlink elsewhere - so one set of bytes answers to both names and rgr can never report a version rigger has moved past.

If rgr already means something else on your machine, the installer says so and leaves it alone; RIGGER_NO_ALIAS=1 skips it outright. cargo install rigger installs rigger only, since cargo builds what the manifest declares and the manifest deliberately declares one binary.

The name is rgr rather than rr, which would have matched the mark: rr is Mozilla’s record-and-replay debugger, packaged in every Linux distribution.

Installer options

Both scripts read these environment variables:

Variable	Effect
RIGGER_VERSION	Install this tag (e.g. v0.1.0) instead of the newest release
RIGGER_INSTALL_DIR	Where the binary lands; defaults to %LOCALAPPDATA%\Programs\rigger on Windows and ~/.local/bin elsewhere
RIGGER_NO_ALIAS	Set to 1 to skip the rgr alias

First run

$ rigger init
Created C:\Users\you\AppData\Local\lacodda\rigger\data\rigger.db (schema version 4)
Next: rigger project add <path>

The database lives in the platform’s local data directory; RIGGER_DATA_DIR overrides it, and rigger doctor prints the path in use.

Record a project

Point rigger at a repository. The project is named after its directory; --name overrides.

$ rigger project add C:\dev\sample
Recorded 'sample' at C:\dev\sample
  remote: https://github.com/acme/sample.git

$ rigger project list
sample  C:\dev\sample

A whole directory of repositories, with their hubs and tags, is one command: rigger adopt.

Check the state

$ rigger doctor
database:  C:\Users\you\AppData\Local\lacodda\rigger\data\rigger.db
schema:    version 4
projects:  1
versions:  0
tasks:     0
sessions:  0
events:    0

Connect your assistant

The record is worth keeping only if it is written as the work happens. Connect the MCP server, and an assistant reads the packet and records what it decides through tools, instead of leaving it in a transcript:

$ claude mcp add rigger -- rigger mcp
Added stdio MCP server rigger with command: rigger mcp to local config

Next steps

• Read the model: projects, versions, tasks, sessions and events.
• See how the context packet replaces reading a hub.
• Understand profiles: one binary at home and at work.