[ ABORT TO HUD ]
SEQ. 1

Automated Reviews with Bugbot

🐛 Bugbot & Code Review 20 min 550 BASE XP

A Reviewer That Never Sleeps

Bugbot is Cursor's automated code reviewer. It analyzes pull request diffs for logic errors, security issues, and edge cases - on GitHub, GitLab, and Bitbucket (including self-hosted). Reviews are powered by Composer 2.5 and typically complete in about 90 seconds.

How It Runs

  • Automatically on every PR update (incremental - re-reviews only what changed)
  • On demand - comment cursor review or bugbot run on the PR
  • As a CI check - the "Cursor Bugbot" status reports success, neutral, or failure so you can gate merges
  • Before you push - run /review, /review-bugbot, or /review-security in the editor; Bugbot syncs via patch IDs so already-reviewed code isn't re-billed on the PR

Autofix

Found a real bug? One click spawns a Cloud Agent to fix it - either on a new branch or pushed to the existing PR branch (up to 3 attempts).

Teaching Bugbot Your Standards

LayerMechanism
Team RulesDashboard-managed, apply across all repos
Repo rulesLearned from feedback + manual: comment @cursor remember [fact] on a PR
BUGBOT.md.cursor/BUGBOT.md files - nest them in subdirectories for area-specific guidance

Usage-based plans can tune effort levels (Default / High / Custom) to trade depth against cost, and Bugbot can call your MCP tools during review on Team/Enterprise plans.

Workflow: Run /review locally before pushing, let Bugbot gate the PR in CI, and use Autofix for the mechanical fixes - human reviewers stay focused on design decisions.
SYNAPSE VERIFICATION
QUERY 1 // 3
How do you trigger a Bugbot review on demand from a PR?
Email support
Comment 'cursor review' or 'bugbot run' on the pull request
Restart CI
It can only run automatically