AI code review comparison
Cursor Bugbot vs Graphite
Cursor Bugbot (PR check plus Cursor editor fixes) against Graphite (Stacked-PR inbox with bundled AI reviews). Billing, hourly throughput, hosts, autofix, and merge-gate claims are dated August 17, 2026.
Cursor
Cursor Bugbot
PR check plus Cursor editor fixes
Graphite
Graphite
Stacked-PR inbox with bundled AI reviews
| Specification | Cursor Bugbot | Graphite |
|---|---|---|
| Vendor | Cursor | Graphite |
| Git hosts | GitHub, GitLab, Bitbucket, Azure DevOps (limited) | GitHub |
| Surface | PR check plus Cursor editor fixes | Stacked-PR inbox with bundled AI reviews |
| Billing model | Usage-based | Per seat |
| Hourly / throughput | Usage-based; API 30–60 req/min | Limited on Hobby/Starter; unlimited on Team |
| Trial | 14-day free trial on all plans (product page). | 30-day trial, or until you upgrade, whichever comes first. After that, unpaid personal repos fall back to Hobby. |
| Config / rules | .cursor/BUGBOT.md; team/repo rules (30k chars each, 100k combined per review) | AI review customizations (automation, filters, rules) — Team and Enterprise |
| Inline comment cap | Not verified | Not verified |
| Self-hosted option | No | Not verified |
| CI hosts | Not a separate CI product | Not a separate CI product |
| Autofix | Yes | Yes |
| Merge gate | No | Not verified |
| Free for qualifying OSS | Not verified | Not verified |
Catalog checked August 17, 2026. Dollar figures and merge-gate behaviour should be re-read on the vendor pricing page before a contract.
Cursor Bugbot
Cursor’s production reviewer: bug-first, not style-first, and wired back into the Cursor editor the team already switched to.
Best for
- Teams already on Cursor who want a PR gate without a second vendor
- Repos where logic bugs matter more than nits
Watch out
Not a substitute for choosing Cursor the editor — that comparison lives under /ai-harnesses. Usage billing means a busy repo can outrun a flat-seat mental model; size spend from cursor.com/pricing#bugbot, not from a third-party $/run table. Requiring the Bugbot check without fail-on-unresolved-issues still allows merge when findings are posted.
Graphite
Buy Graphite for stacked PRs and a merge queue; AI review is bundled into the higher plans rather than sold as a standalone GitHub App.
Best for
- Teams already stacking PRs in Graphite
- Orgs that want review, chat, and merge queue in one inbox
Watch out
GitHub-only (GHES is an Enterprise feature). Limited AI reviews on Hobby/Starter — unlimited is a Team feature. Starter/Team dollar amounts are the annual seat rates on graphite.dev/docs/billing-plans (retrieved 2026-08-17). Older ‘Diamond’ branding still appears in third-party roundups.
Common questions
Cursor Bugbot vs Graphite questions
Answered from the verified figures on this page rather than general guidance.
Where do Cursor Bugbot and Graphite run?
Cursor Bugbot runs as pr check plus cursor editor fixes on GitHub, GitLab, Bitbucket, Azure DevOps (limited). Graphite runs as stacked-pr inbox with bundled ai reviews on GitHub.
How do Cursor Bugbot and Graphite bill?
Cursor Bugbot: Usage-based since the May 2026 change (legacy $40/seat plans renew onto usage billing after 2026-06-08). Individuals consume included usage then on-demand; Teams bill from on-demand spend. Cursor Pro ($20/mo) lists Bugbot on usage-based billing; Teams ($40/user/mo) lists agentic code reviews with Bugbot. Cursor’s May 2026 blog: average run $1.00–$1.50 depending on PR size — that is a vendor average, not a published per-run list price. Confirm live rates at cursor.com/pricing#bugbot. 14-day free trial on the product page. Graphite: Hobby (personal repos, limited AI reviews). Starter $20/seat/month billed annually. Team $40/seat/month billed annually (unlimited AI reviews, customizations, merge queue). Enterprise custom. Figures from graphite.dev/docs/billing-plans (retrieved 2026-08-17), not the marketing HTML snapshot. Limited-tier AI review counts stay unpublished.
What is the hourly or throughput limit for Cursor Bugbot vs Graphite?
Cursor Bugbot: No published hourly PR-review cap. Bugbot API: most endpoints 60 requests/minute per team; POST /bugbot/review 30/minute; dry-run 10/minute. Reviews first consume included usage (Individuals) or on-demand spend (Teams). Autofix uses Cloud Agent credits at plan rates. Higher effort levels cost more usage. Graphite: No published hourly PR cap. Graphite’s pricing matrix lists AI reviews as Limited on Hobby and Starter, Unlimited on Team and Enterprise. Suggested fixes and CI summaries are on the paid matrix. Exact limited-tier counts were not shown on graphite.dev/docs/billing-plans as of 2026-08-17.
Can Cursor Bugbot or Graphite apply fixes?
Cursor Bugbot: Yes. Graphite: Yes. Autofix is still a suggestion until your CI and humans accept it.
Can Cursor Bugbot or Graphite block a merge?
Cursor Bugbot: No. Graphite: Not verified. A missing verification means we did not treat marketing copy as a merge-gate claim.
Should I choose Cursor Bugbot or Graphite?
Choose Cursor Bugbot if this matches: Teams already on Cursor who want a PR gate without a second vendor. Repos where logic bugs matter more than nits. Choose Graphite if this matches: Teams already stacking PRs in Graphite. Orgs that want review, chat, and merge queue in one inbox. Cursor Bugbot watch-out: Not a substitute for choosing Cursor the editor — that comparison lives under /ai-harnesses. Usage billing means a busy repo can outrun a flat-seat mental model; size spend from cursor.com/pricing#bugbot, not from a third-party $/run table. Requiring the Bugbot check without fail-on-unresolved-issues still allows merge when findings are posted. Graphite watch-out: GitHub-only (GHES is an Enterprise feature). Limited AI reviews on Hobby/Starter — unlimited is a Team feature. Starter/Team dollar amounts are the annual seat rates on graphite.dev/docs/billing-plans (retrieved 2026-08-17). Older ‘Diamond’ branding still appears in third-party roundups.