Skip to content
Agents tracked: 258 Downloads (7d): 219M up 6.1% GitHub stars: 5.5M VS Code installs: 148M Releases (7d): 293 Agent pull requests (last week): 937K Updated Oct 7, 2026
Case study PlanetScale

How PlanetScale uses Bugbot as an automated first pass on code review

PlanetScale added Cursor's Bugbot to its pull request workflow to catch logic issues before merge. As reported by Cursor, engineers act on most of its comments.

The problem

AI-assisted coding was producing more code than PlanetScale's reviewers could handle. The company expected it would need to assign engineers to review full time, which would slow product work.

How they did it

  1. Connected Bugbot to the pull request workflow so it reviews each PR automatically.
  2. Used it to catch semantic and logic problems that static analyzers miss, such as state synchronization gaps.
  3. Kept human engineers responsible for addressing the comments and approving merges.

Results

  • As reported by Cursor: 'roughly 80% of Bugbot comments are addressed before merge time'.
  • Bugbot reviews 'more than 2,000 PRs' each month.
  • PlanetScale had estimated it would otherwise need '2 engineers exclusively to code review'.

As reported by the source (Cursor customer story); AgentGid did not measure these figures.

Takeaway. If agents are speeding up code output, add an automated reviewer so human review doesn't become the bottleneck.
AgentGid's take

This suits teams already on pull-request workflows where AI-assisted coding is outpacing reviewers; setup is light, but engineers still have to read and act on every comment. The 80% figure and the 2,000 PRs a month are reported by Cursor, not independently verified, and Bugbot's own pricing isn't in AgentGid's data, only Cursor's plans (Teams $40/user/mo). GitHub Copilot (Free + $10/mo) lists code review in its plans as a cheaper option.

The agent used here

Similar use cases

Guides