Installation

rippy ships as a single static binary. Pick whichever installer you prefer — all four produce the same rippy executable.

Homebrew (macOS and Linux)

brew install mpecan/tools/rippy

This installs the latest release from the mpecan/tools tap.

Cargo (build from source)

cargo install rippy-cli

The crate name is rippy-cli; the binary it installs is called rippy. Requires a recent stable Rust toolchain (edition 2024, Rust 1.93+).

cargo-binstall (prebuilt binaries)

cargo binstall rippy-cli

Downloads the prebuilt binary for your platform instead of compiling from source. Faster than cargo install, no Rust toolchain needed.

GitHub Releases (manual download)

Prebuilt binaries are attached to each GitHub release for:

• macOS Apple Silicon (aarch64-apple-darwin)
• macOS Intel (x86_64-apple-darwin)
• Linux x86_64 (x86_64-unknown-linux-gnu)
• Linux aarch64 (aarch64-unknown-linux-gnu)

Extract the .tar.gz, drop rippy on your PATH, and you are done.

Optional: the rippy-jev build

A separate, opt-in build, rippy-jev, can let a hosted or local decision model approve commands rippy asks about only because it is unsure. It installs the same rippy binary, so install one build or the other. See Model-assisted review for installing and setting it up.

Verify the install

rippy --version

If that prints a version number, you are ready to set up a config.

Next: pick a package

The fastest way to get a working config is to let rippy pick one for you:

rippy init

This walks you through picking a safety package (review, develop, or autopilot) and writes the resulting config to ~/.rippy/config.toml. You can edit or override it at any time.

Then wire rippy into your AI tool of choice — Claude Code, Cursor, Gemini CLI, or Codex CLI.