AI code review comparison
Cursor Bugbot vs Greptile
Cursor Bugbot (PR check plus Cursor editor fixes) against Greptile (Full-repo context PR review). Billing, hourly throughput, hosts, autofix, and merge-gate claims are dated August 16, 2026.
Cursor
Cursor Bugbot
PR check plus Cursor editor fixes
Greptile
Greptile
Full-repo context PR review
| Specification | Cursor Bugbot | Greptile |
|---|---|---|
| Vendor | Cursor | Greptile |
| Git hosts | GitHub, GitLab, Bitbucket, Azure DevOps (limited) | GitHub, GitLab |
| Surface | PR check plus Cursor editor fixes | Full-repo context PR review |
| Billing model | Usage-based | Hybrid |
| Hourly / throughput | Usage-based; API 30–60 req/min | Credits, not hourly |
| Trial | 14-day free trial on all plans (product page). | 14-day Pro trial. |
| Config / rules | .cursor/BUGBOT.md; team/repo rules (30k chars each, 100k combined per review) | Custom rules (Pro) |
| Inline comment cap | Not verified | Not verified |
| Self-hosted option | No | Yes |
| CI hosts | Not a separate CI product | Not a separate CI product |
| Autofix | Yes | Not verified |
| Merge gate | Yes | Not verified |
| Free for qualifying OSS | Not verified | Yes |
Catalog checked August 16, 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.
Greptile
The full-codebase reviewer: it spends credits to keep a graph of the repo, which is the point when bugs live in call sites the diff does not show.
Best for
- Teams whose defects are cross-file, not line-local
- Solo developers who can live on the free 50-credit Starter cap
- Early-stage startups that qualify for the 50% discount
Watch out
Credits run out: 50 standard reviews per seat, then $1 each, and TREX burns three credits. GitHub and GitLab only on the public pricing page. Confirm TREX vs standard before comparing catch-rate anecdotes from third-party blogs.
Common questions
Cursor Bugbot vs Greptile questions
Answered from the verified figures on this page rather than general guidance.
Where do Cursor Bugbot and Greptile run?
Cursor Bugbot runs as pr check plus cursor editor fixes on GitHub, GitLab, Bitbucket, Azure DevOps (limited). Greptile runs as full-repo context pr review on GitHub, GitLab.
How do Cursor Bugbot and Greptile 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. Greptile: Starter: free, 1 active developer, 50 credits/month. Pro: $30/seat/month, 50 credits included per seat, then $1 per extra credit. 1 credit = 1 standard review; 3 credits = 1 TREX review. A seat is any developer who received a Greptile review in that billing period. 14-day Pro trial. Free for qualified MIT/Apache non-commercial OSS. 50% off for pre-Series A startups under $2M trailing-12-month revenue.
What is the hourly or throughput limit for Cursor Bugbot vs Greptile?
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. Greptile: No published hourly cap. Starter: 50 credits/month for one active developer. Pro: 50 credits included per seat/month, then $1 per extra credit. One standard review uses 1 credit; one TREX review uses 3.
Can Cursor Bugbot or Greptile apply fixes?
Cursor Bugbot: Yes. Greptile: Not verified. Autofix is still a suggestion until your CI and humans accept it.
Can Cursor Bugbot or Greptile block a merge?
Cursor Bugbot: Yes. Greptile: Not verified. A missing verification means we did not treat marketing copy as a merge-gate claim.
Should I choose Cursor Bugbot or Greptile?
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 Greptile if this matches: Teams whose defects are cross-file, not line-local. Solo developers who can live on the free 50-credit Starter cap. Early-stage startups that qualify for the 50% discount. 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. Greptile watch-out: Credits run out: 50 standard reviews per seat, then $1 each, and TREX burns three credits. GitHub and GitLab only on the public pricing page. Confirm TREX vs standard before comparing catch-rate anecdotes from third-party blogs.