OpenPR is a GitHub-native control plane for review and scoped implementation work. Start with self-review today, then expand toward contributors, agents, and shared compute without losing context, attribution, or control.
Install the CLI
Ship one command, verify the install, then jump straight into a real PR review flow.
1. Install
npm install -g @jameshiltonbarber/openpr2. Smoke test
openpr help3. Review a PR
openpr review vercel/ai#1046 --provider codex-cli --dry-runInstalls as openpr
Live review inbox
vercel/ai
#1046 Add streaming API support
openstatus/openstatus
#882 Tighten auth token handling
calcom/cal.com
#17811 Repair booking state hydration
# Review handoff
PR: vercel/ai#1046
Focus: close open review threads first
Constraint: keep author intent intact
# PR note
Reply in-thread where possible, then leave one final summary with validation.
# Provenance
reviewer: self-review
provider: codex-cli
mode: supervised
Live GitHub review context
Connect GitHub and load open pull requests, thread queues, and PR conversation state from the repos you can already access.
Review replies and dispatch notes
Inspect the review queue, reply in-thread, and leave a PR-level handoff note without moving the work into a separate coordination tool.
CLI-supported self-review
Use the published CLI to support self-review and shaped handoffs with installable `openpr` workflows.
Product contract
OpenPR should help maintainers work through pull requests where the conversation already lives, not ask them to reconstruct review state somewhere else.
Live inbox
Thread queue
PR-level noteReview is judgment and feedback. Fix work is scoped implementation help. The product should keep those lanes distinct so maintainers can route them differently.
Review = feedback
Fix = scoped executionMaintainers should be able to see who produced a result, how it was produced, and what context or handoff shaped it before they trust it.
reviewer · model · mode
prompt · branch · commandsWho it serves
Keep the review surface familiar while making help easier to shape and trust.
Review stays attached to the PR and its thread history.
Scoped implementation help can be framed without turning into vague backlog churn.
Attribution and provenance remain visible before anything lands.
Pick up clearly shaped work, review with context, and show your work in a way maintainers can evaluate.
Install the CLI and work from real repo and PR context.
Use shaped prompts, branch names, and acceptance constraints instead of guessing.
Build trust through legible review notes and narrowly scoped fixes.
Proof points
Live review workspace
The app can load real pull request context from GitHub, show the active review queue, and keep PR-level and thread-level follow-up in one place.
Trust and attribution
OpenPR keeps reviewer identity, model/vendor context, and execution mode legible so maintainers can assess outputs without flattening everything into one score.
Shaped handoff
Branch names, commands, prompts, and review posture can be shaped from the GitHub context so contributors start from concrete constraints instead of guesswork.
Published CLI
The app remains the GitHub-linked control surface. The CLI is the installable tool contributors can use to inspect shaped work and run review workflows from their own environment.
Install the CLI
Ship one command, verify the install, then jump straight into a real PR review flow.
1. Install
npm install -g @jameshiltonbarber/openpr2. Smoke test
openpr help3. Review a PR
openpr review vercel/ai#1046 --provider codex-cli --dry-runInstalls as openpr
What the CLI is for
How open source support can evolve
The goal is not to turn open source into a generic marketplace. It is to support review and implementation help in ways that remain legible to maintainers, fair to contributors, and grounded in real repository workflows.
A maintainer or contributor can already use OpenPR for self-review against real GitHub context, with the product shaped toward broader open source review support.
Scoped fixes and priced issues can follow naturally once the routing and trust surfaces are stable enough to support explicit budgets and acceptance criteria.
A longer-horizon model where ownership share is derived from code generation share, so contributors who create lasting value can participate in upside.
Start with what works
Connect GitHub, load the live review inbox, and keep the conversation attached to the pull request. Install the CLI when you want a shaped execution surface for contributors or self-review.