Skip to main content
AI Choice Engine
← All AI code review tools

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 retain the source date for each product: Cursor Bugbot October 1, 2026; Graphite October 1, 2026.

Cursor

Cursor Bugbot

PR check plus Cursor editor fixes

vs

Graphite

Graphite

Stacked-PR inbox with bundled AI reviews

Cursor Bugbot versus Graphite specification comparison
SpecificationCursor BugbotGraphite
VendorCursorGraphite
Git hostsGitHub (including GHES), GitLab (including self-hosted), Bitbucket (including Data Center), Azure DevOps Services (public beta), Cursor Origin (documented autofix modes)GitHub
SurfacePR check plus Cursor editor fixesStacked-PR inbox with bundled AI reviews
Billing modelUsage-basedPer seat
Hourly / throughputUsage-based; API 30–60 req/minLimited Hobby/Starter; unlimited Team/Enterprise
Trial14-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 / rulesRoot/nested `.cursor/BUGBOT.md` and team rules; each rule is capped at 30,000 characters and the combined rule context at 100,000 characters per review. Cursor `.mdc` rules under `.cursor/rules` do not apply to BugbotAI review customizations (automation, filters, rules) — Team and Enterprise
Inline comment capNot verifiedUnverifiedNot verifiedUnverified
Self-hosted optionNoNot verifiedUnverified
CI hostsNot a separate CI productNot a separate CI product
AutofixSupported with conditionsNot verifiedUnverified
Merge gateSupported with conditionsNot verifiedUnverified
Free for qualifying OSSNot verifiedUnverifiedNot verifiedUnverified

Cursor Bugbot checked October 1, 2026; Graphite checked October 1, 2026. Dollar figures and merge-gate behaviour should be re-read on the vendor pricing page before a contract.

Usage-based

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. Azure DevOps is currently public beta and limited to Azure DevOps Services, not Azure DevOps Server. Requiring the Bugbot check without fail-on-unresolved-issues still allows merge when findings are posted. Autofix needs storage plus on-demand usage pricing, and its available modes vary by code host (GitHub supports more modes than GitLab/Bitbucket; Azure DevOps autofix is unavailable).

Per seat

Graphite

Consider Graphite for stacked PRs, with limited AI reviews on Hobby/Starter and review customization plus a merge queue on Team/Enterprise.

Best for

  • Teams already stacking PRs in Graphite
  • Team/Enterprise organizations seeking review, chat and a merge queue in one workflow

Watch out

GitHub-only, with GHES listed for Enterprise. Hobby/Starter review counts remain unpublished; unlimited AI reviews, suggested fixes, CI summaries, customization and merge queue are Team/Enterprise features. Suggested fixes do not prove autonomous branch writes. Starter/Team amounts are annual seat rates. Anyone joining the workspace or receiving a Graphite Agent PR review is considered a team member by the pricing FAQ; confirm seat billing for the selected workspace.

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 (including GHES), GitLab (including self-hosted), Bitbucket (including Data Center), Azure DevOps Services (public beta), Cursor Origin (documented autofix modes). 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's May 2026 blog gives a $1.00–$1.50 average run cost depending on PR size; this is a vendor average, not a fixed list price. Cursor's current pricing page lists Pro at $20/month and Teams at $40/user/month, with Bugbot on usage-based billing. Confirm current run rates at cursor.com/pricing#bugbot. 14-day free trial on the product page. Graphite: Hobby is free for personal repositories with limited AI reviews; the current pricing and billing pages do not publish a numeric free-review allowance. Starter is $20/seat/month billed annually with limited AI reviews; Team is $40/seat/month billed annually with unlimited AI reviews; Enterprise is custom. The Team-plan trial lasts 30 days or until upgrade, whichever comes first. Suggested fixes and CI summaries are listed for Team/Enterprise, not every paid plan.
What is the hourly or throughput limit for Cursor Bugbot vs Graphite?
Cursor Bugbot: No published hourly PR-review cap. API limits are endpoint-specific: POST /bugbot/review is limited to 30 requests/minute/team, dry runs to 10/minute/team, and admin API endpoints to 60/minute/team. Dry runs are still billed and persist findings, even though they do not write to the code host. These are API limits, not review allowances. Reviews first consume included usage (Individuals) or on-demand spend (Teams); Autofix uses Cloud Agent credits at plan rates. Graphite: No published hourly PR cap. The current billing matrix lists limited AI reviews on Hobby/Starter and unlimited AI reviews on Team/Enterprise. Neither the free-review count nor the Starter review count is published in the current sources. Suggested fixes and CI summaries are listed on Team/Enterprise.
Can Cursor Bugbot or Graphite apply fixes?
Cursor Bugbot: Yes. Graphite: Not verified. Autofix is still a suggestion until your CI and humans accept it.
Can Cursor Bugbot or Graphite block a merge?
Cursor Bugbot: Yes. 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. Team/Enterprise organizations seeking review, chat and a merge queue in one workflow. 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. Azure DevOps is currently public beta and limited to Azure DevOps Services, not Azure DevOps Server. Requiring the Bugbot check without fail-on-unresolved-issues still allows merge when findings are posted. Autofix needs storage plus on-demand usage pricing, and its available modes vary by code host (GitHub supports more modes than GitLab/Bitbucket; Azure DevOps autofix is unavailable). Graphite watch-out: GitHub-only, with GHES listed for Enterprise. Hobby/Starter review counts remain unpublished; unlimited AI reviews, suggested fixes, CI summaries, customization and merge queue are Team/Enterprise features. Suggested fixes do not prove autonomous branch writes. Starter/Team amounts are annual seat rates. Anyone joining the workspace or receiving a Graphite Agent PR review is considered a team member by the pricing FAQ; confirm seat billing for the selected workspace.