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.
- AI review on existing PRs is the desired output.
Graphite improves code review flow. ProPR turns agent runs into PRs ready for review.
Graphite is closest to the code review and PR velocity layer: stacked changes, PR inbox, merge flow, review tooling, and AI review. ProPR starts one step earlier and continues one step later: it plans the change, implements it in an isolated workspace, opens the pull request, and turns GitHub feedback into new commits.
vs
Graphite
The practical difference
Graphite optimizes the review system around PRs. ProPR optimizes the agent loop that creates and keeps revising those PRs.
Current tool surfaceEditor, hosted workspace, review tool, or trackerWork starts where that product keeps its strongest context.
ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitThe pull request and its review conversation preserve the shared history.
Graphite's core is the stacked pull request: chains of small, dependent PRs where each builds on the last, kept in sync by a stack-aware merge queue and the gt CLI, with a PR inbox and a VS Code extension around them. Its AI reviewer — Graphite Agent (formerly Diamond) — layers codebase-aware feedback and fixes onto that flow. It is a GitHub-only cloud service.
All of that optimizes how people review and merge code. ProPR optimizes the step before the PR exists: it plans the change, runs the chosen agent in an isolated worktree and Docker workspace on your own infrastructure, opens the pull request, and turns review comments into follow-up commits. The two coexist — Graphite can stack and merge the PRs that ProPR opens.
PR velocity layer versus AI implementation loop.
| Question | Graphite | ProPR |
|---|---|---|
| Improve PR queues, stacked changes, and merge flow | Yes | No |
| Run agents to create planned PRs | Limited | Yes |
| Turn review comments into follow-up commits | Different center | Yes |
| Choose Claude, Codex, Antigravity CLI, Mistral Vibe, OpenCode, or APIs per task | No | Yes |
ProPR fits best when...
- Agents write the change and it needs a plan, an isolated workspace, and a PR.
- Plain GitHub comments should request follow-up work, while
/reviewand/fixturn pending AI review suggestions into branch updates. - The two coexist: Graphite can review and merge PRs that ProPR opens and revises.