Cursor Bugbot vs Greptile

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). Greptile runs as full-repo context pr review on GitHub, GitLab, Bitbucket (confirm deployment scope), Cursor Origin (vendor-listed; integration scope not specified), GitHub Enterprise Server (Enterprise), GitLab Self-Managed (Enterprise), Bitbucket Data Center (Enterprise), Gitea (Enterprise), Perforce P4 (Enterprise).

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. Greptile: Starter: free, 1 active developer, 50 credits/month. Pro: $30/seat/month, 50 credits included per seat, then $1 per extra credit. Review tiers: Base (1 credit), Plus (3 credits), Apex (10 credits). 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.

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. 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. A Base review uses 1 credit, Plus 3, and Apex 10.

Cursor Bugbot: Yes. Greptile: Not verified. Autofix is still a suggestion until your CI and humans accept it.

Cursor Bugbot: Yes. Greptile: Not verified. A missing verification means we did not treat marketing copy as a merge-gate claim.

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. Enterprises on Bitbucket Data Center, Gitea or Perforce. 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. 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). Greptile watch-out: Each author has 50 included credits; balances are not pooled. Billing counts completed reviews, not PRs, and attributed CLI reviews share the user's seat/credits; unattributed API/CLI reviews bill as flex without creating an active-developer seat. Base/Plus/Apex use 1/3/10 credits, with $1 per additional credit. A flex-spend cap pauses overage reviews while authors with included credits can continue. Legacy T-Rex is also listed at 3 credits; do not mix its results with other tiers. The homepage lists GitHub, GitLab, Bitbucket and Cursor Origin; confirm the selected integration/deployment scope. Enterprise lists GHES, residency-enabled GitHub Enterprise Cloud, self-managed GitLab, Bitbucket Data Center, Gitea and on-premises Perforce P4.