Cursor Bugbot vs Gitar

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). Gitar runs as pr review plus ci fix loop on GitHub, GitLab, Bitbucket, Azure DevOps.

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. Gitar: Core $20/user/month billed annually ($25 monthly); Pro $40/user/month billed annually ($50 monthly); both capped at 50 users. Enterprise is custom and outcome-based per PR, with unlimited users, custom agreements, bring-your-own Anthropic key, and support for self-hosted code-hosting systems. Pricing now lives on sonarsource.com. 14-day Pro trial, no card. Public GitHub/GitLab repos with an OSI-approved licence can apply for free Pro features. PR summaries are included in Core and higher plans. Merge blocking is Pro, not Core.

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. Gitar: The current vendor page says Enterprise has no rate limits and charges by PR outcome, with unlimited iterations per PR. Core and Pro have published per-user prices and 50-user ceilings, but the current pricing/docs pages reviewed do not state their automatic-review or CI-fix allowance. No separate manual-review or REST API request quota was found in those sources.

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

Cursor Bugbot: Yes. Gitar: Yes. 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 Gitar if this matches: Teams that want CI failure analysis next to the review. Orgs evaluating supervised bot fixes and CI verification. GitHub or GitLab shops evaluating a Sonar-owned reviewer. 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). Gitar watch-out: Core/Pro are capped at 50 users; Enterprise allows unlimited users and is priced by PR outcome, with unlimited iterations per PR. The vendor says Enterprise has no rate limits; it does not publish a Core/Pro automatic-review allowance on the sources checked. Merge blocking is Pro, not Core. Gitar supports GitHub, GitLab, Bitbucket and Azure DevOps, including self-hosted code-hosting instances; this does not establish that the Gitar service itself runs on-premises.