Hey, thanks for the pushback and for the detailed codebase analysis.
Fair point, my previous reply was too generic. There are a few forum reports with the same pattern (a steady 9 to 15 minutes even on small PRs). The latency is usually isolated to the bug detection step:
- BugBot reviews take 9–12 minutes on small PRs — latency isolated to bug detection step (req ID included)
- BugBot review runtime ~9–12 minutes per PR — normal or something off?
So diff size isn’t the only factor, and I can’t share an ETA on a fix yet.
To tie your specific runs into the investigation, can you run bugbot run verbose=true as a comment on a fresh PR where this reproduces, then paste the serverGenReqId_... here (both would be ideal, from @luchillo17 and @rushil)? With those IDs we can pull the logs for your exact runs and confirm whether it’s the same bottleneck step or different root causes.
On Autofix cost (@luchillo17), usage is billed against your main plan’s Cloud Agent quota at the normal rates, and you can see it in the Dashboard alongside other agent runs. That way you can track it in real time and only enable Autofix on important comments so you don’t burn through your budget.