Cursor Bugbot
Usage BasedCursor's AI bug finder for pull requests.
Published 27 September 2026
Scores
Popularity3/5
The Cursor name is widely known and Bugbot reviews more than two million pull requests a month, but the reviewer itself is known mainly to Cursor users and teams comparing AI code review tools.
Learning Curve1/5
Enabling it is a toggle in the Cursor dashboard plus a Git app install, and it reviews the next pull request with no rules written. BUGBOT.md files are optional context.
Flexibility3/5
Nested BUGBOT.md rules, team rules, and effort levels let teams steer what it looks for, but the models and review style are Cursor's choice and it only covers GitHub and GitLab.
Performance4/5
Reviews run automatically on each update and got about three times faster in a mid-2026 update; Cursor reports developers resolving around 80% of flagged bugs by merge, with the high effort setting finding more on complex changes.
Portability2/5
Works on any repository on GitHub or GitLab, but setup and billing are tied to a Cursor account, rules live in Cursor-specific BUGBOT.md files, and Autofix depends on Cursor's cloud agents.
About Cursor Bugbot
Cursor Bugbot is the pull request reviewer from Anysphere, the company behind the Cursor editor. It installs on GitHub, GitHub Enterprise, or GitLab and reviews each pull request as it is opened and updated, or on demand when someone comments bugbot run or uses the /review command. Its focus is narrower than a general-purpose reviewer: it looks for logic bugs, edge cases, and security problems rather than style.
Project context comes from BUGBOT.md rule files in the repository's .cursor folder, which can be nested per directory, plus team-wide rules set once for an organisation. Effort levels trade review depth for cost, with a high setting that finds more issues on complex changes. Each finding links straight into the Cursor editor, and Autofix can hand a finding to a Cursor cloud agent that tests a fix in its own virtual machine and pushes it to the branch.
Bugbot reviews any repository regardless of which editor or agent wrote the code, but it needs a Cursor account for setup and billing. Since mid-2026 it is billed by usage, drawn from a plan's included usage on individual plans and from on-demand spend on team plans, with an average review costing roughly a dollar to a dollar and a half. Cursor folded Graphite's code review product into Bugbot after acquiring Graphite in December 2025, and Bugbot now reviews more than two million pull requests a month.
Key Features
- Automatic reviews on every PR update, or on demand via bugbot run or /review
- Focus on logic bugs, edge cases, and security issues rather than style
- Project rules in nested .cursor/BUGBOT.md files plus organisation-wide team rules
- Adjustable effort levels, including a high setting for complex changes
- Links from each finding straight into the flagged code in Cursor
- Autofix hands findings to a cloud agent that tests and pushes a fix
- Supports GitHub, GitHub Enterprise, and GitLab
Pros
- Developers resolved about 80% of flagged bugs before merge in Cursor's published figures
- One click from a finding to a fix in the editor or a cloud agent
- Usage billing means small teams pay only for the reviews they run
- Reviews any repository, not only code written in Cursor
Cons
- Requires a Cursor account and plan even for teams that don't use the editor
- Per-review billing adds up quickly on repositories with many pull requests
- Pricing follows Cursor's plan changes, such as the 2026 switch from a flat seat fee to usage billing
Cursor Bugbot Pricing
Usage Based- · Bugbot billed from the plan's included usage
- · Average review costs $1 to $1.50 depending on PR size
- · Per user, Teams Standard seat
- · Bugbot billed from on-demand spend
- · Centralized billing and shared team rules
- · Custom pricing
- · GitHub Enterprise support and admin controls
Tech Stacks with Cursor Bugbot
Cursor Dev Stack
DeveloperCursor as both the editor and the coding agent, with Grok as the default model and Claude, OpenAI, or Gemini available from the same model picker, plus your pick of GitHub or GitLab for version control.
Devin Dev Stack
DeveloperDevin Desktop as the editor and agent manager, with Devin Cloud for work that keeps going without your machine, Claude as the default model and OpenAI, Gemini, or Grok in the same picker, plus your pick of GitHub or GitLab for version control.
Development
LLM
Claude Code Dev Stack
DeveloperClaude Code as the coding agent, in the terminal, the desktop app, an IDE extension, or the browser, running on Claude, with your pick of GitHub or GitLab for version control.
Development
LLM
Tools Related to Cursor Bugbot
Integrates with Cursor Bugbot(2)
Cursor Bugbot installs as a GitHub App on selected repositories and posts its bug findings as comments on pull requests.
Cursor Bugbot reviews GitLab merge requests as well as GitHub pull requests, extending the same bug-focused review to teams outside the GitHub ecosystem.
Required by Cursor Bugbot(1)
Cursor Bugbot is set up and billed through a Cursor account and plan with no standalone sign-up, though the editor itself never needs to open — Bugbot reviews pull requests on GitHub or GitLab whatever wrote the code.
Alternatives to Cursor Bugbot(2)
Cursor Bugbot is a bug-focused reviewer that lives inside a Cursor plan, where CodeRabbit is an independent subscription that walks through every part of the PR — Bugbot suits teams already paying for Cursor.
Cursor Bugbot's per-review pricing inside an existing Cursor plan is lighter to start than Greptile's per-credit seats, but Greptile brings whole-codebase context and a self-hosted option that Bugbot lacks.
Learning Resources
No resources yet — check back soon.
Vendor
Anysphere
Website →Tags
Details
- Maintained
- Yes
- Primary languages
- JavaScript, TypeScript, Python, Go, Java, Rust
- Open source
- No
- AI features
- Agent