Rules you can read
A Breakspec rule is a sentence someone on your team agreed to. When it breaks, you get the example that broke it.
Compare · Checked 12 October 2026
Bugbot is Cursor’s pull request reviewer. It looks for bugs, can fix them, and learns rules from how your team reacts to its comments. Breakspec’s rules work differently: a person approves each one, and Breakspec checks it by running your code.
A Breakspec rule is a sentence someone on your team agreed to. When it breaks, you get the example that broke it.
Your agent can suggest rules, but they wait for a person to approve them. Until then they can warn you, but never block a merge.
Breakspec checks code from Claude Code, Codex, Cursor or a person.
| Cursor Bugbot | Breakspec | |
|---|---|---|
| How it finds bugs | An AI reads the change | Runs your code on hundreds of examples |
| What you get back | A comment about what might be wrong | An example that breaks your code, which you can run yourself |
| Who decides what “correct” means | The AI, guided by your instructions | You, by approving rules |
| Cost of checking every pull request | About $1.00 to $1.50 per run, by Cursor’s figures | No AI cost. Rechecking doesn’t use AI |
| After a fix | Reviews the new code again | Reruns the example that failed, and notices if the fix cheats |
Yes. Bugbot catches what looks wrong. Breakspec checks what your rules say must always be true, and then checks the fix.
Checked on 12 October 2026, from Cursor Bugbot’s own docs and pricing pages. Prices and features change; if something here is out of date, tell us at sales@breakspec.com and we’ll fix it.