AI code review for pull requests
BugBot automatically reviews your PRs and catches potential bugs and issues. It uses the same AI that powers Cursor Agent to catch issues that humans might miss.
To set up BugBot, you need Cursor admin access and GitHub org admin access.
Connect GitHub
(or Manage Connections
if already connected)After installing, you’ll see available installations and their enabled repositories. Enable or disable BugBot per repository. BugBot only runs on your personal PRs.
Customize how BugBot works:
cursor review
or bugbot run
on a PRAfter installing, you’ll see available installations and their enabled repositories. Enable or disable BugBot per repository. BugBot only runs on your personal PRs.
Customize how BugBot works:
cursor review
or bugbot run
on a PRAfter installing, team admins will see a list of available installations and their enabled repositories. Team admins can enable or disable BugBot per repository, setup allow/denylists for reviewers, and configure settings:
Once enabled, BugBot will run for anyone contributing to the repository, whether or not they’re on your team.
Individual Team members can customize how BugBot works:
cursor review
or bugbot run
on a PRBugBot analyzes PR diffs using Cursor’s most powerful models. When it finds potential issues, it leaves comments with detailed explanations and fix suggestions.
cursor review
, bugbot run
, or cursor run
in a PR commentProvide additional context to BugBot by creating .cursor/BUGBOT.md
files in your repository. These files help BugBot understand your project’s specific patterns, conventions, and areas of focus during code review.
BugBot automatically includes relevant context from .cursor/BUGBOT.md
files during code review:
.cursor/BUGBOT.md
file in your repository root is always included in BugBot’s context.cursor/BUGBOT.md
it encounters along the wayThis hierarchical approach allows you to provide both project-wide guidance and specific context for different areas of your codebase.
Organize BugBot rules by placing .cursor/BUGBOT.md
files throughout your project:
Use BugBot rules to:
Example .cursor/BUGBOT.md
:
BugBot is available for $40 per user per month (20% off for yearly billing) for both teams and individuals.
Teams pay $40 per user per month based on actual BugBot usage:
Team admins can set hard limits on the maximum number of BugBot seats allowed per month to control costs and prevent unexpected charges.
Sign up for the paid version of BugBot through your team dashboard to enable billing and start using BugBot for your team’s pull requests.
Teams pay $40 per user per month based on actual BugBot usage:
Team admins can set hard limits on the maximum number of BugBot seats allowed per month to control costs and prevent unexpected charges.
Sign up for the paid version of BugBot through your team dashboard to enable billing and start using BugBot for your team’s pull requests.
Individual users pay a simple flat rate of $40 per month for unlimited BugBot reviews on all pull requests they author.
This covers all repositories and pull requests where you’re the author, with no per-review or usage-based charges.
Subscribe to BugBot through your individual account settings to start receiving AI code reviews on your pull requests.
If BugBot isn’t working:
cursor review verbose=true
(or bugbot run verbose=true
) on your PR for detailed logging and request IDWhen reporting issues, include the request ID from verbose mode output for faster debugging.
Is BugBot privacy-mode compliant?
Yes, BugBot follows the same privacy mode compliance as Cursor. It processes data the same way as any other Cursor request.