BugBot stopped working in GitLab repo

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

Plan: Enterprise
Integration: GitLab.com

Problem:
BugBot has stopped triggering in some of our repos. It previously worked, last confirmed working on June 16, 2026 at 14:44:26 CEST. We don’t know the exact date it stopped.

What we’ve tried:

  • verbose=true - produces no output
  • Toggling BugBot off/on for the repo - no effect
  • Manual trigger - does not work either

Webhook logs (GitLab side):
GitLab shows webhooks are being delivered and returning HTTP 200, but the response body is empty. Response headers include gRPC-related headers (Grpc-Status, Grpc-Message, Grpc-Status-Details-Bin), suggesting the request reaches the backend but is silently dropped.

We can provide the app ID used in the webhook configuration on request.

BugBot works correctly for our other repos, only some of them repo are affected. Nothing has changed on our side that we’re aware of. In some other repo we’ve seen in logs Error: Net::ReadTimeout but this one is clear.

Steps to Reproduce

It’s webhook in our Gitlab, so reproducing is not possible.

Expected Behavior

Bugbot should trigger automatically & manually and do his job.

Operating System

Other

Version Information

Just bugbot

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @Krystof_Saml!

I saw you worked through this over e-mail support. Hope it’s alright that I share what worked here, so other users can benefit.

  1. In GitLab, go to Settings, Webhooks, and delete any webhook whose URL points to api2.cursor.sh/gitlab_webhook (delete all of them if you see duplicates).
  2. In GitLab, go to Settings, Access Tokens, and revoke the Cursor-owned project access token (usually named something like “Cursor Bugbot”).
  3. In the Cursor dashboard, disable BugBot on that repo, wait a few seconds, then re-enable it.