Same first pass every PR gets, without a per-seat bill. Your infrastructure, your model keys, your choice of provider.
MIT licensed. Hosting and AI usage on you.
Switch providers by changing one setting. Your GitHub workflow stays the same.
How it works
One deploy. After that, every pull request follows the same path inside GitHub. No extra dashboard, no per-seat bill from PR Agent.
Step 1
Install PR Agent beside the rest of your stack. Your GitHub credentials and AI keys stay in your account, not a vendor dashboard.
Your servers · your keys
Step 2
PR Agent starts a review on opening or approval, depending on your settings. Your team sees a reaction on the pull request so everyone knows work has begun.
Starts on opening or approval
Step 3
PR Agent looks at the branch and the changes, then hunts for bugs and correctness issues. When risky APIs show up, it also checks for security problems.
Review runs on your servers
Step 4
Notes appear next to the changed lines, plus a short summary in the conversation. Want more? Comment /describe, /ask, /triage, or mention the App bot. Replies stay in the same thread.
/review · /describe · /ask · /triage
Step 5
Docs-only pull requests can take a lighter path. Very large changes may get a partial review, and PR Agent says what it could not cover instead of faking completeness.
Partial review notice when needed
Use cases
The same summary, description, ask, and triage formats PR Agent posts on a real pull request. Pick a command to see what lands.
/reviewFour specialists read the branch and the diff for correctness, security, quality, and tests. One orchestrator decides what is worth posting.
pr-agent bot commented just now
PR Agent Review
Note
| Size | M |
|---|---|
| P1 · c4 | Webhook ack can race the durable write |
| P2 · c3 | Summary edit ignores stale head guard |
| Mergeability | Two-way: trivial to revert; only error-message rendering. |
| Blast radius | Localized: stream error text only; no API, schema, or control-flow change. |
| Follow-ups | 1. Remove the retry feature flag once metrics confirm the fix 2. Delete the legacy dispatcher path once the batched dispatcher ships |
Verify each finding against current code. Fix only still-valid issues./describeTurn a blank description into a type, summary bullets, a changes diagram, and a file walkthrough.
pr-agent bot commented just now
PR Agent Description
PR Type
Enhancement, Documentation
Description
Changes Diagram
flowchart LR
Webhook --> Intake --> Queue --> ReviewWorkerFile Walkthrough
src/settings/constants.ts
docs/configuration.md
/askAsk about the code without leaving GitHub. Comment /ask followed by your question, or mention the App bot.
pr-agent bot commented just now
Question: Why is the retry wrapper needed around the webhook dispatcher?
Answer:
Transient GitHub 502s were dropping webhook deliveries before durable intake completed. The retry wrapper keeps the delivery alive long enough for the Postgres write and acknowledgement reaction to finish, then the worker picks up the agent work item.
Without it, a delivery that failed on the first attempt was gone for good. GitHub does not redeliver on its own, so the pull request stayed quiet even though the webhook had been accepted.
/triagePreview the would-be diff, then apply the approved set. Bare /triage still fixes without a preview.
pr-agent bot commented just now
PR Agent Triage
Full PR triage.
Evaluated head: c4f8a91b2e3d4a5b6c7d8e9f0a1b2c3d4e5f6a7b
1 Fixed · 1 Already resolved · 0 Skipped · 1 Dismissed · 0 Previously resolved
Pushed commits:
a1b2c3d Fix webhook ack race (1 file, +12 −3)| Severity | Finding | Location | Verdict | Thread |
|---|---|---|---|---|
| P1 | Webhook ack can race the durable write | src/webhooks/intake.ts L148 | Fixed a1b2c3d | thread |
| P2 | Summary edit ignores stale head guard | src/review/publish.ts L91 | Already resolved | thread |
| P2 | Docs-only path skips durable ack wait | src/webhooks/intake.ts L162 | Dismissed | thread |
Policy suggestions for dismissed findings
Commit these to .pr-agent/*.mdc to steer future reviews:
Create .pr-agent/src-webhooks-intake.mdc with:
---
globs:
- "src/webhooks/intake.ts"
alwaysApply: false
---
Intentional: docs-only PRs skip the durable ack wait by design.Commands
Ask from a pull request comment, or let the automatic path run when a pull request opens.
/reviewRuns on opening or approval, depending on your settings, or when you comment /review on an open pull request.
Comments land next to the lines that need attention.
Then, after every push
/verifyRuns after each new push when that option is left on, or when you comment /verify.
With no open findings, verification skips the agent. An older-head run completes degraded instead of clean. Switch to on-demand to limit token use.
/describeRuns when a pull request opens in auto mode, or when you comment /describe.
Summary bullets and optional visual sketches go into the PR body when the diff proves them.
/askComment /ask … or mention the GitHub App bot with your question.
The word @bot only matches if you named the App that. /ask does not need a mention. Asking the same comment twice posts one answer; post a new comment to ask again.
/triageComment /triage, or /triage preview then /triage all, on the pull request.
Preview the would-be diff, then apply the approved set. Bare /triage still fixes without a preview.
Pricing
Know the cost before you connect GitHub or add an AI provider.
$0
No credit card, no per-seat fee, and the whole thing is open source under MIT.
You cover the server, database, and model bills. Extra developers cost nothing.
Run it inside your network, pick your provider, and keep traffic under your rules.
Compare
CodeRabbit, Greptile, Cursor Bugbot, and Macroscope sell hosted review. PR Agent is for teams that want the reviewer, the AI keys, and the review data in their own account.
| Criteria | PR Agent | CodeRabbit | Greptile | Cursor Bugbot | Macroscope |
|---|---|---|---|---|---|
| Runs on your servers | Yes | Partial | Partial | No | No |
| Open source, MIT | Yes | No | No | No | No |
| No per-seat fee | Yes | No | No | No | Yes |
| Bring your own model keys | Yes | No | No | No | No |
| Choose the model provider | Yes | No | No | No | No |
| Review data stays in your account | Yes | Partial | Partial | No | No |
| Reviews GitHub pull requests | Yes | Yes | Yes | Yes | Yes |
| Whole-repository index | Partial | Yes | Yes | Partial | Yes |
| PR description, ask, and fix commands | Yes | Yes | Partial | No | Partial |
PR AgentYesPR AgentYesPR AgentYesPR AgentYesPR AgentYesPR AgentYesPR AgentYesPR AgentPartialPR AgentYesFAQ
Find your starting point here. If your question is missing, open an issue and it gets answered in the repository.
PR Agent is open-source software that reviews GitHub pull requests on servers you run. You deploy it once, connect GitHub and an AI provider, and it posts reviews, summaries, and answers back on the pull request.
Yes. It reviews pull requests, leaves comments on the changes, writes summaries, and responds to commands in GitHub. Unlike CodeRabbit’s hosted product, PR Agent runs on your servers with your credentials and your AI keys.
Greptile is a cloud reviewer that indexes whole repositories. PR Agent is self-hosted and looks at each pull request from the branch and what changed. Pick it when you want to run the reviewer and choose the model provider, not another managed subscription.
PR Agent fits teams that want bug and correctness reviews on GitHub without sending that work through a hosted IDE-tied review service. Bugbot stays tied to the Cursor IDE. PR Agent is a review system you operate with your own model keys.
Macroscope is a hosted AI code review product for GitHub pull requests. PR Agent offers a similar automatic review flow as MIT-licensed software you deploy yourself. You choose the models and where review data is processed.
Yes. PR Agent is MIT-licensed with no per-seat fee from us. You pay for hosting and AI usage. Add 50 developers and the PR Agent software bill stays at $0.
PR Agent works with OpenAI, Anthropic, Google, DeepSeek, OpenRouter, Groq, and more via the Pi provider catalog. You pick the provider and set your own API key on the machine that runs reviews.
Yes for now. PR Agent connects as a GitHub app, reviews pull requests, and replies in GitHub comments. GitLab and Bitbucket are not supported yet.
PR Agent checks the saved result and available evidence. If it cannot confirm the result, it stops that run rather than repeat the change. An unpublished review gets the usual failure notice with /review guidance. An existing published summary is kept. Failed or incomplete evidence reads can still retry. Recovering a run does not use another retry unless PR Agent starts another work attempt. Interrupted work attempts still count; previously failed runs are not reopened automatically.
On a VPS you control, then put HTTPS in front of the web process. A panel such as Dokploy or Coolify can give you a domain and a certificate. Hetzner is a common cheap pick. Hostinger and DigitalOcean also work. The App still needs the same Compose stack. The panel does not replace it.
Installation
You need Docker, a GitHub App, and one AI provider key. GitHub must reach your host over HTTPS.
Step 01
Register the app, generate a private key, then install it on the test repo. Creating the app is not enough. If you pick only selected repositories, include that repo.
Full steps are in README Installation.
Step 02
Copy the example env. Paste the generated App private key as one line, the webhook secret, and a provider key. Then start PR Agent with Compose. The example key is not a real key.
cp .env.example .env# Fill a real one-line GitHub App PEM, WEBHOOK_SECRET,# and your provider keydocker compose builddocker compose up -dMinimum keys to set
GITHUB_APP_ID=...GITHUB_APP_PRIVATE_KEY=...WEBHOOK_SECRET=...PI_PROVIDER=openaiPI_MODEL=gpt-4o-miniOPENAI_API_KEY=sk-...Step 03
Open a pull request on an installed repo. Comment /help as a repo owner, member, or collaborator. Other accounts get no reply even though GitHub accepted the webhook.
/reviewRun a full review; repeated commands acknowledge active work, even when cancellation races intake/describeWrite a readable summary into the PR body/verifyRecheck open findings/cancelCancel a queued or running review/review forceRestart the review on the latest commit/helpList available commands/ask …Ask a question about the code in that thread/triageApply fixes and push. Preview is optional./triage previewShow the would-be unified diff. Nothing is pushed./triage allApply the previewed set for this head. Refused without a matching preview.reviewer yourselfClone the repository, fill one env file, and start the stack with Compose. The first review lands on your next pull request.
git clone https://github.com/prathamdby/pr-agent