BugBot reviews take 9–12 minutes on small PRs — latency isolated to bug detection step (req ID included)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)
BugBot

Describe the Bug

BugBot reviews are consistently very slow (~9–12 minutes), even on relatively small PRs.

We investigated locally and found that the latency is almost entirely in the “bug detection” phase rather than context gathering or rule loading.

This is occurring via the GitHub integration (not Cursor IDE or CLI).

Steps to Reproduce

  1. Open a PR (even with small diff size)
  2. Let BugBot run via GitHub checks
  3. Observe total runtime (~9–12 minutes)
  4. Expand BugBot details and inspect timing breakdown

Expected Behavior

BugBot reviews should complete in a few minutes, especially for small PRs.

Screenshots / Screen Recordings

image (3)
image (3)1032×654 53.6 KB

Operating System

N/A (runs via GitHub integration / Background Agent)

Version Information

N/A (not using Cursor IDE or CLI — this is BugBot via GitHub)

For AI issues: which model did you use?

Unknown (BugBot internal model)

For AI issues: add Request ID with privacy disabled

Request ID:
serverGenReqId_1b1456ca-2af2-404d-a819-5b3ed8d43f01

Additional Information

We verified the following:

  • Only one BugBot file:
    apps/octogen-voyager/.cursor/BUGBOT.md

  • Contents are minimal (no links or external references):

    • Use Pydantic models instead of dicts
    • Look for encapsulation violations
    • Look for DRY violations
    • Look for duplicated code

  • No root-level .cursor/BUGBOT.md

  • We are not linking to any .md or .mdc files

  • .cursorignore is configured

  • Regular .cursor/rules/*.mdc files exist but are not referenced by BugBot

Timing breakdown from BugBot UI:

  • Gathered PR context: 3s
  • Completed bug detection: 7m 52s
  • Posted results: 1s

Observation:
Nearly all latency is in the bug detection phase, not repo scanning or rule loading.

This suggests the bottleneck may be in the model/inference step rather than repository configuration.

Does this stop you from using Cursor?

Sometimes - I can sometimes use Cursor

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.