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 need Cursor admin access and GitHub org admin access.

1. Go to cursor.com/dashboard
2. Navigate to the BugBot tab
3. Click Connect GitHub (or Manage Connections if already connected)
4. Follow the GitHub installation flow to install the app
5. After setup, return to the dashboard to enable BugBot on specific repos where you can configure settings

​

Configuration

• Individual
• Team

​

Per GitHub installation

After installing, you’ll see available installations and their enabled repositories. Enable or disable BugBot per repository. BugBot only runs on your personal PRs.

​

Personal

Customize how BugBot works:

• Only Run when Mentioned: Start BugBot manually, by commenting cursor review or bugbot run on a PR
• Only Run Once: Run BugBot only once per PR, even if new commits are added

​

Per GitHub installation

After installing, you’ll see available installations and their enabled repositories. Enable or disable BugBot per repository. BugBot only runs on your personal PRs.

​

Personal

Customize how BugBot works:

• Only Run when Mentioned: Start BugBot manually, by commenting cursor review or bugbot run on a PR
• Only Run Once: Run BugBot only once per PR, even if new commits are added

​

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, setup allow/denylists for reviewers, and configure settings:

• Only Run Once: Run BugBot only once per PR per installation, even if new commits are added

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:

• Only Run when Mentioned: Start BugBot manually, by commenting cursor review or bugbot run on a PR
• Only Run Once: Run BugBot only once per PR, even if new commits are added

​

How BugBot Works

BugBot analyzes PR diffs using Cursor’s most powerful models. When it finds potential issues, it leaves comments with detailed explanations and fix suggestions.

• Automatic Comments: BugBot re-runs and comments on every PR update
• Manual Trigger: Run BugBot manually with cursor review, bugbot run, or cursor run in a PR comment
• Fix in Cursor: Use “Fix in Cursor” links in comments to jump into Cursor with full context preloaded

​

BugBot Rules

Provide 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.

​

How BugBot rules work

BugBot automatically includes relevant context from .cursor/BUGBOT.md files during code review:

• Repository root: The .cursor/BUGBOT.md file in your repository root is always included in BugBot’s context
• Directory hierarchy: When reviewing a changed file, BugBot looks upward through the file’s directory hierarchy and includes every .cursor/BUGBOT.md it encounters along the way

This hierarchical approach allows you to provide both project-wide guidance and specific context for different areas of your codebase.

​

File structure

Organize BugBot rules by placing .cursor/BUGBOT.md files throughout your project:

project/
  .cursor/BUGBOT.md          # Always included (project-wide rules)
  backend/
    .cursor/BUGBOT.md        # Included when reviewing backend files
    api/
      .cursor/BUGBOT.md      # Included when reviewing API files
  frontend/
    .cursor/BUGBOT.md        # Included when reviewing frontend files

​

Example usage

Use BugBot rules to:

• Highlight security considerations specific to your project
• Explain domain-specific patterns and conventions
• Point out common pitfalls in particular areas of your codebase
• Provide context about architectural decisions
• Define coding standards and best practices

Example .cursor/BUGBOT.md:

# Project Review Guidelines

## Security Focus Areas
- Always validate user input in API endpoints
- Check for SQL injection vulnerabilities in database queries
- Ensure proper authentication on protected routes

## Architecture Patterns
- Use dependency injection for services
- Follow the repository pattern for data access
- Implement proper error handling with our custom error classes

## Common Issues
- Memory leaks in React components (check useEffect cleanup)
- Missing error boundaries in UI components
- Inconsistent naming conventions (use camelCase for functions)

​

Pricing

BugBot is available for $40 per user per month (20% off for yearly billing) for both teams and individuals.

​

Troubleshooting

If BugBot isn’t working:

1. Enable verbose mode: Comment cursor review verbose=true (or bugbot run verbose=true) on your PR for detailed logging and request ID
2. Check permissions: Ensure BugBot has proper repository access
3. Verify installation: Make sure the GitHub app is installed and enabled for your repo

When reporting issues, include the request ID from verbose mode output for faster debugging.

​

FAQ