Hi @JacobNisnevich Thank you for reporting and I apologize for the inconvenience.
I looked into the webhook deliveries and this appears to be a server-side issue with our GitLab BugBot integration, not anything specific to your local Cursor version or OS.
The webhooks are reaching Cursor, but some GitLab webhook events are timing out or failing while BugBot processes them. We are actively tracking this and working on a fix. Will keep you posted on the status of the issue.
We’re having similar issues with Cursor <> GitLab integrations and automations across the board. But Bugbot not doing reviews at all or timing out is what brought me here.
Any webhook automation we’re trying to make for Gitlab is failing. And the MCP integration seems to error all the time - though I have a dirty workaround making Cursor use an instance of glab CLI tool to work on merge requests via API.
EDIT:
Example Bugbot issue: It placed 4 duplicated comments saying “Cursor Bugbot has reviewed your changes using high effort and found 3 potential issues.” - instead of saying what those 3 potential changes are as usual.
We’re running into the same issue with webhooks - tagging @cursor is failing frequently. Usually to resolve I have to go into Cursor, resync the repos, then completely sign out and sign back in to force it to work again.
