Bugbot surfaces bugs.
Hyrax architects the system.
Bugbot reviews pull requests for bugs and hands off to Cursor for the change, which is a fast loop for a team already living in that editor. Hyrax runs continuously over the whole repository and delivers changes that are verified before anyone opens them.
- Hyrax audits roughly 400 of its own repositories.
- Free plan: full access, up to 100 PR reviews a month, a $30 starter credit, and $10/month ongoing.
Verified end to end, with no Bugbot handoff
What changes when Hyrax runs above the tools.
The codebase, not the diff
Bugbot sees the change in front of it. Hyrax audits the whole repository, so problems that no single pull request touches still surface.
Verified before it arrives
Every change runs the project baseline tests, build and lint, and passes a second reviewer agent, before the pull request exists.
Context that compounds
The map of the codebase lives in the repository and strengthens with every merge, so the next decision starts from everything learned before it.
How Hyrax and Bugbot make decisions.
| Decision criteria | Bugbot | Hyrax |
|---|---|---|
| Unit of work | The pull request, scanned for likely bugs. | The whole repository, audited continuously across six domains. |
| Codebase context | Reads the diff with repository context from Cursor. | A durable map committed to the repository as HYRAX.md and .hyrax/discovery, so it strengthens as the codebase changes. |
| Output type | Bug comments on the pull request, with changes handed to the editor. | Verified pull requests, plus issues ranked by severity and effort. |
| Verification | Issues are advisory. The team validates each one. | Baseline tests, build, lint and a second reviewer agent run against the project itself before a pull request opens. |
| Human control | The team resolves and merges. | A human approves and merges every pull request. Hyrax never merges on its own. |
| Delivery surface | GitHub pull requests, handing off to the Cursor editor. | GitHub pull requests, with issues and posture in the Hyrax console. |
| Pricing model | Add-on to Cursor, commonly around $40 per user per month. | Free plan with a $30 starter credit and $10/month ongoing. Paid is $30 per user per month and each paid user gets $30/month of credits. |
Read how Bugbot describes itself: cursor.com/bugbot(opens in a new tab)
Comments on a diff, or a verified pull request.
- 01A pull request opens and Bugbot reads the diff.
- 02Bugbot returns comments, summaries and suggested changes.
- 03The team interprets the feedback, makes the edits, and merges.
- 01Maps the codebase and keeps the map in the repository
- 02Applies architectural judgment across six domains
- 03Opens a verified pull request that a human merges
GitHub-native. Human-controlled. Verified before merge. No training on customer code.
From install to the first verified pull request.
Install the GitHub App
Grant read access to the repositories in scope. No card is required to start.
Hyrax maps the repository
Discovery writes HYRAX.md and .hyrax/discovery into the repository, so humans and AI tools read the same context.
Review the first pull request
Approved upgrades arrive as verified pull requests. A human merges every one.
Both tools solve real problems.
Choose Bugbot if
The team is standardised on Cursor and wants bug catching in the pull request with a one-click path back into the editor. Bugbot fits that loop well.
Choose Hyrax if
Bugs in open pull requests are only part of the picture. Hyrax audits the whole codebase across six domains and returns changes that already passed the project tests and build.
Add-on to a Cursor subscription.
Free plan with a $30 starter credit and $10/month ongoing. Paid is $30 per user per month, and each paid user gets $30/month of credits.
Questions about Bugbot and Hyrax.
Does Hyrax work alongside Bugbot?
Yes, and most teams run both. Bugbot keeps doing its job. Hyrax works at the level of the whole codebase, decides what is worth changing, and delivers verified pull requests. Nothing about the Bugbot setup has to change.
What does Hyrax change in the repository?
Discovery writes HYRAX.md and a .hyrax/discovery directory, which document the architecture, conventions and risk areas of the codebase. Everything else arrives as a normal pull request on its own branch. Hyrax has no write access to the default branch.
How does pricing work?
The free plan includes full access, a $30 starter credit and $10/month of credits ongoing, with no card required. The paid plan is $30 per user per month, and each paid user gets $30/month of credits. Pull request reviews are included on every plan.
What happens after signup?
Installing the GitHub App and granting access to a repository takes a few minutes. Hyrax maps the codebase, then runs the first audit and returns issues ranked by severity and effort. The first verified pull requests follow once an audit is approved.