BugBot Not Finding All Bugs First Pass

Support Help
,
1

Hey,

A bunch of the developers on my team have complained that BugBot is not finding the majority of bugs on the first or even subsequent runs. Currently BugBot takes about 12-15 mins to complete which would be ok, if it found everything. I often hear things from my developers like, it found a low severity formatting issue or similar and I fixed it, next run it found 2 medium severity issues in a completely different file, I fixed those and then it found a high severity one in a complete different section of code. Had to go back and forth 5-6 times before the PR had no reported issues and was ready to merge. At 15 mins between pushes, it takes all day to get a PR in a state where it can be human reviewed.

Is there anything we can do with the BugBot.md file or something that will help reduce this friction with developers? I tried AutoFix but the same issue was occurring after fixes were accepted.

Thanks,
Jake

1 Like
3

Hey @Jacob_Steele this is a known issue that several teams have reported. BugBot sometimes surfaces findings bit by bit across multiple passes instead of catching everything at once.

There’s an existing thread with more context and discussion here: Bugbot doesn't catch all issues on first pass - multiple review cycles needed

A couple of workarounds that can help reduce the back-and-forth:

  • Comment cursor review on the PR to manually trigger a re-check. This can surface more findings without needing a new commit.
  • In the .cursor/BUGBOT.md file, try adding clear instructions to focus on high and medium severity issues and to be thorough on the first pass, like: “Report all issues found across all changed files in a single review. Prioritize high and medium severity bugs over formatting suggestions.”

These are workarounds though. The core issue is on our radar and the team is aware. No ETA yet, but reports like yours from teams where this affects daily workflow help with prioritization.

If you can share a link to a specific PR where this happened, that’d be useful for the team to investigate further.

4

Thanks, this has been a very high pain point for us, to the point were we are already investigating other products. The cycle simply becomes to long to be considered effective. I am not able to share our internal code with a non team member. Hopefully you can provide a work around sooner rather than later.