Bugbot reviews the diff. Grace reads the repository.
Cursor's Bugbot runs automatically on every pull request, comments on what it finds, and can push a fix to the branch. It is good, and it overlaps with Grace more than anything else on this site. The difference is stated in Cursor's own documentation: Bugbot analyses the pull request diff, not the whole repository.
What Cursor is for
- Writing and changing code faster than you would by hand
- Keeping a developer in flow across a large codebase
- Agents that carry out a change you described, in the editor
- Being the place the work actually happens
None of this is a criticism. Cursor does it well, and Grace doesn't do it at all.
What Grace is for
- The state of the whole application, not the delta of one branch
- Risk ranked across everything found, by what sits on a path that matters
- Running whether or not anyone is committing this week
- Production errors traced back to a cause and returned as a corrective PR
- Written for whoever pays for the app, not only for whoever can read the diff
And Bugbot is a real code reviewer
Read off their own documentation in August 2026.
This is the closest thing to Grace that any of the three ship, and pretending otherwise would be silly. If you have a team opening pull requests all day, Bugbot is doing a job that needs doing.
- It runs automatic reviews on every pull request update, and can be triggered by commenting on a PR.
- It leaves comments with explanations and fix suggestions, and posts a CI check status.
- Autofix can push a fix to the existing branch or to a new one.
- It connects to GitHub including Enterprise Server, GitLab including self-hosted, and Bitbucket including Data Center.
- It reads the existing comments on a PR to avoid repeating a suggestion someone already made.
A diff is not a codebase
Cursor's documentation is explicit: Bugbot reviews branch changes relative to the base branch and does not analyse the entire repository, only the PR diff and its context. Two questions follow from that, and Bugbot answers neither.
- What is already wrong? Everything that shipped before Bugbot arrived was never in a diff it saw. An app built with AI last year has its whole surface in that category.
- What happens when nobody opens a PR? The apps that hurt people are usually the ones nobody has touched in four months. No changes means no reviews.
- A diff cannot show you that this function is the third-most-changed file in the repo, or that the person who wrote it left. Risk that comes from history needs the history.
- Reviewing a change well is not the same as knowing which of your forty open risks to close first. Ranking needs to see all of them at once.
Where the two stop overlapping.
| Cursor | With Grace | |
|---|---|---|
| What is analysed | The pull request diff and its context | The whole repository |
| What triggers it | A pull request, or a command on one | Pushes, PRs, a schedule, a Sentry alert |
| Code that predates it | Not reviewed until it appears in a diff | In scope from the first audit |
| An app nobody is changing | No diffs, so no reviews | Still watched, still reported on |
| Ranking across findings | Per pull request | Across the codebase, by business impact |
| Who it is written for | The developer | Whoever owns the app |
| Where the work happens | In your editor, by you | In a branch, proposed to you |
Checked against Cursor's own documentation in August 2026. These products ship monthly. If something here is out of date, tell us and we will correct it.
Using both is the normal case.
These two genuinely stack. Bugbot guards the change while a developer is making it; Grace guards the application the changes accumulate into. If your team lives in Cursor, keep Bugbot on every PR and let Grace answer the question no diff can: given everything that is in there, what breaks first.
The five deliverables, in order →
What we keep finding in Cursor repos
When you don't need Grace.
The audit is free, so the worst case is an hour and a report. But there are situations where the answer is simply no, and we would rather say so here than after you have paid.
- You have a team of engineers, everything ships through reviewed pull requests, and someone owns production. Bugbot on its own may be all you need.
- The codebase is new, small, and entirely written under review. There is no accumulated state for Grace to find yet.
- You want an AI that writes features. That is Cursor's job, and Grace does not do it.
What people ask about the two.
Everything outside the diff. Bugbot tells you whether this change is safe; Grace tells you what state the application is in, including the code that shipped before either tool existed and the code nobody has opened a pull request against in months. On a repository built with AI, that is most of it.
They comment on different things, at different moments. Bugbot reviews the diff as it is proposed. Grace's pull requests are its own work, opened against risks it found by reading the repository, and they arrive with the reasoning attached. If you run both, Bugbot will review Grace's PRs, which is a sensible arrangement.
Probably not, and that is worth saying. Cursor is a developer's editor. If nobody on your side writes code, the comparison that matters is with the tool that built your app, not with the tool a developer would have used.
Point Grace at the repo Cursor produced.
The audit is free and nothing gets rebuilt. In minutes you'll know what will break first.