Bugbot in Cursor quietly got a lot smarter and we are here for it

Bugbot — Cursor's built-in pull request reviewer — has picked up a handful of genuinely useful upgrades. The headline is Autofix: when Bugbot flags a bug in your PR, it can now spawn a Cloud Agent (an AI that runs in the background on Cursor's servers) to write the fix, push it to a branch, and hand it back to you. No copy-pasting suggestions. No switching context. Just a fixed branch waiting for your approval.

That is the part most people will notice first. But the less obvious additions are just as useful.

You can now tell it how hard to think

Bugbot has three Effort Levels. Default is fast and cheap — good for catching obvious mistakes without burning through your usage quota. High is slower and more thorough, the kind of pass you want before merging something important. Custom lets you write your own trigger condition: something like "go deep when the PR touches authentication or payments." You pick the level per review, or set a default for the whole team.

The pricing model shifted in May 2026 from per-seat to usage-based, which means Effort Levels now have a direct cost implication. Running High effort on every PR would add up. Running it only where it matters is the smarter play.

It gets smarter the more your team uses it

Bugbot can now learn from your team's PR activity — more like building a memory of what your codebase cares about than following a static checklist. You can also teach it directly by commenting @cursor remember [fact] on any PR, and that fact becomes part of how it reviews future diffs. Team Rules, repository rules, and a project-level .cursor/BUGBOT.md file all feed into it, with a clear hierarchy so conflicts resolve predictably.

If you are thinking "that sounds like a lot of config to set up" — it is optional. Out of the box it just reviews. The rules layer is there when you want consistency across a team.

Review locally, skip the duplicate on GitHub

There is a /review-bugbot skill inside Cursor that lets you run a Bugbot review before you even push. If you then open a PR with the same diff, Bugbot on GitHub recognizes it and skips the remote review. One pass, not two. For solo developers who want the feedback earlier in the process, this is probably the most immediately practical change.

Bugbot also reads existing PR comments before it posts, so it will not repeat something another reviewer already caught. Small thing. Appreciated.

Tools 1

More on vibe coding
  1. Tutorial What does Cursor want a beginner WordPress vibe-coder to know before starting out?
  2. Tutorial We asked Cursor docs how a beginner should actually start and this is what they said
  3. Tutorial Cursor added a whole separate window for agents and it changes how you work
  4. Example Cursor Agent with no tool call limit looks a lot like having a developer on your team
  5. Tutorial Cursor Agent does a lot more than write code for you
  6. Tutorial Get to know Cursor before you start vibe coding your next project
  7. Tutorial Vibe-coded WordPress themes break in predictable ways and most of them are avoidable
  8. Debate Some things you should vibe code. Some things you really should not.
  9. Discussion These are the voices that actually made vibe coding a thing people learn