Bugbot run stuck or non responsive from IOS remote control

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

I have two consecutive PRs done using the IOS app with remote control to local laptop where

  1. one time the Bugbot (which is on for the repo) just does not start, even after prompting @cursor review. I have a Request ID - serverGenReqId_1869c2c9-8b32-4752-a51b-44c5339571c1 with Bugbot run verbose=true

  2. the next consecutive PR I will see in the UI in github but it never kicked off and started
    “Cursor BugbotExpected — Waiting for status to be reported”. Bugbot request id: serverGenReqId_ab74dc2f-b7fc-4f8b-bc8e-47fe85456367

Note it could be just bugbot being down and I happened to be using mobile remote control

Steps to Reproduce

Using remote control to open PRs

Expected Behavior

I have consistently used bugbot and autofix on the repo in local IDE and cloud agent and it has worked

Screenshots / Screen Recordings

Image 1-7-26 at 9.48 AM.png
Image 1-7-26 at 9.48 AM.png2000×1104 255 KB
Image 1-7-26 at 9.49 AM.png
Image 1-7-26 at 9.49 AM.png2000×1104 153 KB

Operating System

MacOS

Version Information

Cursor IOS v1.0.0 (37904)

For AI issues: which model did you use?

Composer 2.5 but not relevant

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey there!
This isn’t anything to do with iOS remote control. BugBot runs entirely server-side off GitHub webhooks when a PR is opened or when you comment @cursor review, so it makes no difference whether you created the PR from the iOS app driving your laptop or from the desktop directly. Remote control never touches the BugBot path.

Both PRs look like BugBot just didn’t kick off its run on those specific commits, which happens intermittently and isn’t a problem with your setup or plan. A couple of ways to get it going again:

  • Comment @cursor review as a new top-level comment on the PR (not a reply to an existing comment), or
  • Push a new commit to the branch.

On the second PR, “Cursor Bugbot — Expected — Waiting for status to be reported” is GitHub saying it’s still waiting on the BugBot check for that commit (it’s a required check in your branch protection, which is why the merge is blocked). Once a fresh run reports its status, that clears on its own.

If it happens again on a specific PR, drop the PR link here or at [email protected] and we’ll dig into the logs for that exact run.