Installation¶
Get rp1 installed in under 5 minutes. This guide covers all platforms and AI assistants.
Prerequisites¶
Before installing rp1, ensure you have:
- Git 2.15+: Required for worktree isolation in
build-fast. Check withgit --version.
Upgrading Git
Download from git-scm.com or use:
Step 1: Install the rp1 CLI¶
The rp1 CLI provides tools for installing plugins and managing your setup. Install it first, then add plugins for your AI assistant.
Homebrew (Recommended)
Alternative: Install Script
Homebrew (Recommended)
Alternative: Install Script
Step 2: Verify CLI Installation¶
You should see the version number (e.g., 0.2.1). If you get "command not found", see Troubleshooting below.
Step 3: Initialize Your Project¶
Navigate to your project directory and run init:
This interactive command will:
- Create the
.rp1/directory structure - Detect your AI assistant (Claude Code or OpenCode)
- Inject rp1 instructions into
CLAUDE.mdorAGENTS.md - Configure
.gitignorefor rp1 artifacts - Install plugins automatically (for Claude Code)
- Verify the installation
- Display next steps
Expected output:
The init command displays a step-by-step wizard with real-time progress:
rp1 init Step 6 of 8
✓ Loading tools registry
└─ Registry loaded successfully
✓ Checking git repository
└─ At repository root
✓ Setting up directories
└─ Created .rp1/context/
└─ Created .rp1/work/
✓ Detecting AI tools
└─ Found: Claude Code v2.0.75
✓ Configuring instruction file
└─ Updated CLAUDE.md
◐ Installing plugins...
└─ Installing rp1-base...
○ Verifying installation
○ Health check
When complete, you'll see a summary with next steps:
✨ rp1 initialized successfully!
Detected Tools:
✓ Claude Code v2.0.75
Setup Status:
✓ .rp1/ directory
✓ CLAUDE.md configured
✓ .gitignore configured
✓ Plugins installed
Next Steps:
→ 1. Restart Claude Code to load plugins [required]
○ 2. Build knowledge base
Run: /knowledge-build
Analyzes your codebase for AI context awareness
○ 3. Create project charter
Run: /blueprint
Captures project vision to guide feature development
Documentation: https://rp1.run
Multi-Tool Detection
If you have both Claude Code and OpenCode installed, rp1 will detect and configure plugins for both tools automatically. The summary will show all detected tools and their configuration status.
CI/Automation
For non-interactive environments (CI pipelines, Docker builds, scripts), use rp1 init --yes to accept all defaults and install plugins automatically.
Non-TTY mode features:
- No ANSI color codes (clean, parseable output)
- No animated spinners (static progress lines)
- Sensible defaults for all prompts
- Standard exit codes (0=success, 1=failure)
Example CI output:
[1/8] Loading tools registry... done
[2/8] Checking git repository... done
[3/8] Setting up directories... done
[4/8] Detecting AI tools... Claude Code v2.0.75
[5/8] Configuring instruction file... done
[6/8] Configuring .gitignore... done (recommended preset)
[7/8] Installing plugins... done
[8/8] Health check... done
rp1 initialized successfully!
See Non-Interactive Mode for CI/CD integration examples.
Step 4: Restart Your AI Tool¶
Required: Restart Your AI Assistant
You must restart your AI assistant (Claude Code or OpenCode) to load the newly installed plugins. Without restarting, rp1 commands will not be available.
Manual Plugin Installation
If init couldn't install plugins (e.g., OpenCode, or if you skipped installation), you can install them manually:
Deprecated Syntax
The old colon-separated syntax (rp1 install:claude-code, rp1 install:opencode) is deprecated. Use rp1 install <tool> instead.
Step 5: Verify Plugins¶
If successful, you'll see output like READY [single-project] or READY [monorepo: N projects].
Next Steps¶
You're ready to go! Continue to Your First Workflow to run your first rp1 command.
Troubleshooting
Command not found after CLI installation?
Ensure the install directory is in your PATH:
If not found, add to your shell config:
Commands not appearing after plugin installation?
- Claude Code: Make sure you completely restarted Claude Code
- OpenCode: Verify plugins exist at
~/.opencode/prompts/rp1-base/
Permission denied during installation?
Install to a user directory instead:
Knowledge build takes a long time?
First-time builds analyze your entire codebase and can take 10-15 minutes for large projects. Subsequent builds are incremental (2-5 minutes).
Still having issues?
Check GitHub Issues or open a new issue.
Advanced Options
Pin to specific version:
Custom install directory:
Manual checksum verification:
# Download binary and checksums
curl -LO https://github.com/rp1-run/rp1/releases/download/v0.2.1/rp1-darwin-arm64
curl -LO https://github.com/rp1-run/rp1/releases/download/v0.2.1/checksums.txt
# Verify (macOS)
shasum -a 256 -c checksums.txt --ignore-missing
# Verify (Linux)
sha256sum -c checksums.txt --ignore-missing
Direct download links:
- GitHub Releases
- macOS:
rp1-darwin-arm64(Apple Silicon) orrp1-darwin-x64(Intel) - Linux:
rp1-linux-arm64orrp1-linux-x64 - Windows:
rp1-windows-x64.exe
Updating:
Uninstalling:
Security Notes
rp1 binaries are not code-signed. Your operating system may warn you about running them.
macOS Gatekeeper
If macOS shows "cannot be opened because the developer cannot be verified":
- Open System Settings > Privacy & Security
- Scroll down to find the rp1 warning
- Click Allow Anyway
- Run
rp1again and click Open
Or use the terminal:
Windows SmartScreen
If Windows shows "Windows protected your PC":
- Click More info
- Click Run anyway