Graphite fits best when...
- Stacked PRs, review queues, and merge velocity are the bottleneck.
- Humans write most of the code and need a faster review system around it.
- You already pay for Cursor and want its cloud agents inside the review inbox.
ProPR and Graphite: agent-built PRs ready for stacked review
Graphite owns review and merge: stacked changes, the gt CLI, a merge queue, and Graphite Agent reviews. ProPR feeds that layer: it plans and implements the change on your server, then turns PR feedback into commits.
vs
Graphite
Before and after the review
Graphite optimizes the review system around PRs, and its agent runs are Cursor's hosted agents on a Cursor plan. ProPR optimizes the self-hosted agent loop that creates and keeps revising those PRs with any of five agents.
Graphite pathStacked pull requests → Graphite Agent review → merge queueGraphite starts once the pull request exists.
ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitProPR builds the pull request that enters the stack and keeps revising it.
Graphite's core is the stacked pull request: chains of small, dependent PRs kept in sync by the gt CLI and a stack-aware merge queue, with a PR inbox around them. Graphite Agent, the renamed Diamond reviewer, comments on each PR with codebase-aware findings and suggestions that a human commits. Cursor announced its agreement to acquire Graphite in December 2025; Graphite still sells its own plans, from a free Hobby tier to Team at $40 per user per month, and its Agents feature runs Cursor Cloud Agents on a paid Cursor plan, committing straight to the branch of a PR you authored. It is a GitHub-only cloud service.
All of that optimizes how people review and merge code. ProPR owns the step before the PR exists: it plans the change, runs the agent in isolation on your own infrastructure, opens the pull request, and turns review comments into follow-up commits. The two coexist: Graphite stacks and merges the PRs that ProPR opens.
PR velocity layer versus AI implementation loop.
| Question | Graphite | ProPR |
|---|---|---|
| Owner and license | Proprietary; Cursor agreed to acquire it in December 2025 | Apache 2.0, self-hosted |
| Stacked PRs, review inbox, and merge queue | Yes | No |
| Runs agents to implement a change | Cursor Cloud Agents, on a paid Cursor plan | Claude Code, Codex, Antigravity CLI, Mistral Vibe, OpenCode on your server |
| Plan approval before code | No | Yes |
| Review comments become follow-up commits | Reviewer posts suggestions a human commits; Cursor agents commit to the author's branch | Any plain comment, any agent |
| Git hosts | GitHub only | GitHub only |
ProPR fits best when...
- Agents write the change and it needs a plan, an isolated workspace on your server, and a PR.
- Plain GitHub comments request follow-up work, while
/reviewand/fixturn AI review findings into branch updates. - You want both: Graphite reviews and merges the PRs that ProPR opens and revises.
Verified November 2026: Cursor acquisition announcement, Graphite pricing, Graphite AI review comments, Graphite Agents, Graphite GitHub docs.
Use Graphite with ProPR.
Stays in Graphite
- Stacked pull requests, the
gtCLI, the PR inbox, and the merge queue. - Graphite Agent review comments on every pull request.
- Cursor Cloud Agents inside the inbox, if you pay for Cursor.
Moves to ProPR
- The plan and the implementation before the pull request exists, on your server with the agent you choose.
- Follow-up commits for review comments, from any of five agents.
- Branch updates from base with
/merge, so the pull request reaches the queue mergeable.
Wire them together
Install ProPR and keep Graphite installed
Run propr setup (quickstart) or pick a ProPR Hosted plan, add the repository, and sign in your agent. Graphite keeps its GitHub installation.
Let ProPR open the pull requests
Add the AI label to an issue and approve the plan. The pull request ProPR opens enters your Graphite inbox and stacks like any other.
Keep the stack moving
A plain comment becomes the next commit; /merge updates the branch from base and resolves conflicts before the queue. The merge conflict playbook shows it on one pull request.