Skip to main content

​
One-line install

The fastest way to install Rampart: 
curl -fsSL https://rampart.sh/install | bash
The curl installer drops the binary in ~/.local/bin and runs rampart quickstart automatically.

​
Pin a specific version

By default, the installer downloads the latest release. To pin a specific version: 
RAMPART_VERSION=v0.7.0 curl -fsSL https://rampart.sh/install | bash

​
Alternative installation methods

Install via Homebrew (macOS and Linux):
brew install peg/rampart/rampart
After installing via Homebrew, run rampart quickstart to set up the background service and agent hooks.

​
Verify installation

Check that Rampart is installed correctly: 
rampart version
You should see output like: 
rampart v0.7.0 (commit abc1234)

​
Platform-specific notes

macOS System Integrity Protection (SIP) blocks LD_PRELOAD for binaries in /usr/bin/. This doesn’t affect AI agents, which typically live in:
  • Homebrew: /opt/homebrew/bin/ or /usr/local/bin/
  • nvm: ~/.nvm/versions/node/
  • pyenv: ~/.pyenv/versions/
  • cargo: ~/.cargo/bin/
rampart preload works fine with these.
The install script sets up a systemd user service:
# Check service status
systemctl --user status rampart-serve

# View logs
journalctl --user -u rampart-serve -f

# Restart service
systemctl --user restart rampart-serve
The service starts automatically on boot.
If you get an error running the install script, you may need to allow script execution:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
This only affects the current user and doesn’t require admin rights.After installation, Rampart is added to your user PATH at ~/.rampart/bin.
If rampart isn’t found after installation, add the install directory to your PATH:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

​
What’s installed

The installation process:
  1. Downloads the binary to ~/.local/bin/rampart (or ~/.rampart/bin/rampart.exe on Windows)
  2. Verifies the SHA-256 checksum to ensure integrity
  3. Adds to PATH (on Windows, updates user PATH environment variable)
  4. Runs rampart quickstart to set up the background service and detect agents
The one-line installer runs rampart quickstart automatically. If you install via Homebrew or Go, you’ll need to run rampart quickstart manually.

​
Upgrading

Upgrade to the latest version: 
rampart upgrade
This downloads the latest binary and refreshes built-in policies. Your custom rules in ~/.rampart/policies/custom.yaml are never overwritten.
To upgrade without updating policies:
rampart upgrade --no-policy-update

​
Uninstalling

Remove Rampart completely: 
rampart uninstall
This removes:
  • The binary
  • Background service (systemd/launchd)
  • Agent hooks
  • Configuration and audit logs (after confirmation)
Uninstalling removes all audit logs by default. Back up ~/.rampart/audit/ if you need to keep them.

​
Next steps

Quick start

Set up Rampart for your agent in under 2 minutes

Agent integration

See detailed setup instructions for your specific agent

Build docs developers (and LLMs) love

Get started for freeTalk to us