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’ll need Cursor admin access and GitHub org admin access.
Connect GitHub
(or Manage Connections
if already connected)We’ve been using BugBot internally for months and it’s proven valuable at finding subtle bugs
You can setup a monthly spending limit for BugBot in $USD. This will count towards your global spending limit.
After installing, you’ll see a list of available installations and their enabled repositories. You can enable or disable BugBot per repository. BugBot will only run on your personal PRs.
Customize how BugBot works for you:
bugbot run
on a PRYou can setup a monthly spending limit for BugBot in $USD. This will count towards your global spending limit.
After installing, you’ll see a list of available installations and their enabled repositories. You can enable or disable BugBot per repository. BugBot will only run on your personal PRs.
Customize how BugBot works for you:
bugbot run
on a PRTeam admins can setup a monthly spending limit for BugBot in $USD. This will count towards your team’s global spending limit.
After 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 for them:
bugbot run
on a PRUnder the hood, BugBot looks at the diffs in your commits and analyzes the code using the most powerful models in Cursor. When a potential issue is found, it leaves a comment with a detailed explanation and a suggestion for a fix.
bugbot run
in a comment on the PRUnder the hood, BugBot uses the same AI that powers Cursor and use same pricing as Max mode.
If BugBot isn’t working as expected, try these steps:
bugbot run verbose=true
on your PR to get detailed logging and a request IDWhen reporting issues to support, always include the request ID from verbose mode output, this helps us debug much faster.