Everything you need to install, configure, and use Plip.
Visit github.com/apps/plip-io and install Plip on your repositories. You can grant access to all repos or select specific ones.
On install, Plip automatically creates a blue plip label on all granted repositories and posts a welcome issue with a quick-start guide.
Add the plip label to any issue. Plip takes it from there.
Plip requests the minimum permissions needed to do its job:
| Permission | Access | Why |
|---|---|---|
| Contents | Read & Write | Clone your repo and push fix branches |
| Issues | Read & Write | Read issue details and post progress updates |
| Pull Requests | Read & Write | Create PRs with the fix |
| Metadata | Read | Access repository info (language, default branch, etc.) |
Plip uses a two-phase triage-guided agent architecture. Each phase uses the right model for the job.
Claude Haiku quickly scopes the issue. It reads the bug report, scans the codebase, and produces a structured triage:
Claude Sonnet executes the fix plan from Phase 1:
Model selection is automatic. Haiku handles triage, Sonnet handles most fixes, and Opus tackles complex issues on Business/Enterprise plans. No configuration needed.
Progress is posted to the issue as a single comment, updated in real-time so you can follow along.
Human review is always required. Plip creates PRs, never pushes directly to your main branch.
Plip works out of the box with zero configuration. To customize behavior, add a
.github/plip.yml file to your repository.
All fields are optional.
# Trigger mode: "label" waits for the plip label, "auto" processes every new issue
trigger: label
# Label name that triggers a run (only used when trigger is "label")
label: plip
# Issue types to process: "bug", "feature", or "all"
issue-type: bug
# Language override: "auto" detects from your repo
language: auto
# Skip test execution
skip-tests: false
# Override auto-detected build command
buildCommand: ""
# Override auto-detected test command
testCommand: ""
Set trigger: auto to have Plip process every new issue automatically, without requiring a label.
If ScrumChum is installed on the same repo (detected by scrumchum: labels), auto-trigger mode waits 60 seconds for triage to complete before starting a fix. This gives Plip better context for the fix plan.
Add the plip label to any issue. Plip investigates the bug and creates a PR with the fix.
Set trigger: auto in your config. Every new issue automatically triggers Plip.
Plip responds to labels and webhooks. There are no slash commands.
Plip auto-detects your language and package manager. Here are the languages with first-class support:
npm, yarn, pnpm, bun
pip, poetry
go modules
cargo
maven, gradle
dotnet
bundler
cmake, make
Plip can handle any language with a standard build and test setup. The languages above have optimized auto-detection for package managers and test runners.
All plans use Claude Sonnet. Business and Enterprise unlock Claude Opus for complex issues.
| Plan | Price | Fixes/mo | Repos | Model | Queue Priority |
|---|---|---|---|---|---|
| Free | $0 | 10 | 1 | Haiku | Standard |
| Pro popular | $39/mo | 25 | Unlimited | Sonnet | High |
| Business | $399/mo | 100 | Unlimited | Sonnet + Opus | Higher |
| Enterprise | $599/mo | 250 | Unlimited | Sonnet + Opus | Highest |
Code is cloned temporarily and the container is destroyed after the job completes. No permanent storage of source code.
Container network access is limited to the GitHub API and Anthropic API only. No other outbound connections.
All incoming webhooks are verified against GitHub's signature to prevent unauthorized triggers.
All traffic is encrypted in transit. No unencrypted connections are accepted.
AI processing runs via the Anthropic Claude commercial API. Anthropic does not train on data sent through the API.
When you uninstall Plip, all associated data is removed. Nothing is retained.
Install Plip in 30 seconds. Your first 10 fixes are free, every month.
Install on GitHub