Cursor Bugbot (PR check plus Cursor editor fixes) against GitHub Copilot code review (Built into GitHub.com pull requests). Billing, hourly throughput, hosts, autofix, and merge-gate claims retain the source date for each product: Cursor Bugbot October 1, 2026; GitHub Copilot code review October 1, 2026.
Cursor
Cursor Bugbot
PR check plus Cursor editor fixes
vs
GitHub
GitHub Copilot code review
Built into GitHub.com pull requests
Cursor Bugbot versus GitHub Copilot code review specification comparison
Review-specific trial terms are not stated in the code-review documentation; check the selected Copilot plan's eligibility.
Config / rules
Config / rules
Root/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 Bugbot
Cursor Bugbot checked October 1, 2026; GitHub Copilot code review 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).
Bundled with another product
GitHub Copilot code review
The default if the team already pays for Copilot: no second GitHub App, no second vendor review.
Best for
Teams standardised on GitHub Copilot
Business/Enterprise orgs enabling policy-gated reviews for unlicensed members
Watch out
Shares credit pools with the rest of Copilot. Unlicensed-member reviews bill directly to the organization and are not attributed to an individual budget; Actions minutes may also apply. Azure DevOps and Copilot approvals are public previews. Enabled approvals can satisfy required-approval rules, but this is conditional and was not runtime-tested here. Current docs list Lite as the built-in default and Balanced for some owners; inspect the effective effort rather than assume a universal switch. Balanced consumes more credits. Compare review findings on representative PRs before paying for a second reviewer.
Cursor Bugbot vs GitHub Copilot code review questions
Answered from the verified figures on this page rather than general guidance.
Where do Cursor Bugbot and GitHub Copilot code review 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). GitHub Copilot code review runs as built into github.com pull requests on GitHub, Azure DevOps (public preview).
How do Cursor Bugbot and GitHub Copilot code review 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. GitHub Copilot code review: Bundled with Copilot plans that include code review (Pro lists access to cloud agent and code review, with $15 monthly credits on Pro). Licensed-user review draws from the Copilot allowance. Orgs can enable review on PRs from people without a Copilot seat; that usage bills as GitHub AI Credits. From 2026-06-01, code-review workflows also consume GitHub Actions minutes.
What is the hourly or throughput limit for Cursor Bugbot vs GitHub Copilot code review?
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. GitHub Copilot code review: No published hourly PR cap. GitHub docs estimate Lite reviews at $0.05–$1 of AI credits and Balanced at $0.25–$5, plus GitHub Actions minutes for agentic context gathering (self-hosted runners do not consume Actions minutes). Business/Enterprise reviews stop when a relevant user, enterprise or cost-center budget is exhausted. Copilot Free does not include GitHub pull-request review; organization-enabled access for unlicensed members is billed separately.
Can Cursor Bugbot or GitHub Copilot code review apply fixes?
Cursor Bugbot: Yes. GitHub Copilot code review: Yes. Autofix is still a suggestion until your CI and humans accept it.
Can Cursor Bugbot or GitHub Copilot code review block a merge?
Cursor Bugbot: Yes. GitHub Copilot code review: Not verified. A missing verification means we did not treat marketing copy as a merge-gate claim.
Should I choose Cursor Bugbot or GitHub Copilot code review?
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 GitHub Copilot code review if this matches: Teams standardised on GitHub Copilot. Business/Enterprise orgs enabling policy-gated reviews for unlicensed members. 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). GitHub Copilot code review watch-out: Shares credit pools with the rest of Copilot. Unlicensed-member reviews bill directly to the organization and are not attributed to an individual budget; Actions minutes may also apply. Azure DevOps and Copilot approvals are public previews. Enabled approvals can satisfy required-approval rules, but this is conditional and was not runtime-tested here. Current docs list Lite as the built-in default and Balanced for some owners; inspect the effective effort rather than assume a universal switch. Balanced consumes more credits. Compare review findings on representative PRs before paying for a second reviewer.