BugBot
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.
Setup
To set up BugBot, you’ll need Cursor admin access and GitHub org admin access.
- Go to cursor.com/settings
- Navigate to the Integrations tab
- Click
Connect GitHub
(orManage Connections
if already connected) - Follow the GitHub installation flow to install the app
- After setup, return to Integrations to enable BugBot on specific repos where you can configure settings
We’ve been using BugBot internally for months and it’s proven valuable at finding subtle bugs
Configuration
Spending limit
You can setup a monthly spending limit for BugBot in $USD. This will count towards your global spending limit.
Per GitHub installation
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.
Personal
Customize how BugBot works for you:
- Only Run when Mentioned: Start BugBot manually, by commenting
bugbot run
on a PR - Only Run Once: Run BugBot only once per PR, even if new commits are added
- Hide “No Bugs Found” Comments: Don’t post comments when BugBot finds no issues
Spending limit
You can setup a monthly spending limit for BugBot in $USD. This will count towards your global spending limit.
Per GitHub installation
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.
Personal
Customize how BugBot works for you:
- Only Run when Mentioned: Start BugBot manually, by commenting
bugbot run
on a PR - Only Run Once: Run BugBot only once per PR, even if new commits are added
- Hide “No Bugs Found” Comments: Don’t post comments when BugBot finds no issues
Spending limit
Team admins can setup a monthly spending limit for BugBot in $USD. This will count towards your team’s global spending limit.
Per GitHub installation
After installing, team admins will see a list of available installations and their enabled repositories. Team admins can enable or disable BugBot per repository and setup allow/denylists for reviewers. Once enabled, BugBot will run for anyone contributing to the repository, whether or not they’re on your team.
Personal
Individual team members can customize how BugBot works for them:
- Only Run when Mentioned: Start BugBot manually, by commenting
bugbot run
on a PR - Only Run Once: Run BugBot only once per PR, even if new commits are added
- Hide “No Bugs Found” Comments: Don’t post comments when BugBot finds no issues
How BugBot Works
Under 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.
- Automatic Comments: Every time a PR is updated, BugBot re-runs and leaves comments with potential issues.
- Manual Trigger: You can also run BugBot manually with
bugbot run
in a comment on the PR - Fix in Cursor: Use the “Fix in Cursor” links in comments to jump straight into Cursor with full context preloaded.
Pricing
Under the hood, BugBot uses the same AI that powers Cursor and use same pricing as Max mode.
Troubleshooting
If BugBot isn’t working as expected, try these steps:
- Enable verbose mode: Comment
bugbot run verbose=true
on your PR to get detailed logging and a request ID - Check permissions: Ensure BugBot has proper access to your repository
- Verify installation: Make sure the GitHub app is installed and enabled for your repo
When reporting issues to support, always include the request ID from verbose mode output, this helps us debug much faster.