Gitlab self-hosted : repos provisionning issue

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Hello,
We are on a Teams Plan, and I am Team Admin.
I am trying to integrate Bugbot into our self hosted Gitlab, where I am Admin.

I followed Cursor Bugbot wizard completely, choosing 1 repository at first. As there is no MR in this repo, I then enabled all others in bugbot dashboard settings.
I then tested commenting in a MR @bugbot run or @cursor bugbot run, which did nothing. In both cases, when typing “@”, Gitlab did not mention any user. I checked into users, and I see only 1 cursor project bot was created, on the inital repo I selected in the wizard.
I saw reports of gitlab integration creating a lot of project bots (ex: GitLab integration support - #6 by janario), so the behavior I’m seeing seems definitely not correct.

Also, I don’t know if it is linked or not, but I’m not seeing any organization category in Bugbot dashboard Team settings (See picture) vs what it is supposed to look like : How do I turn off bugbot auto-fix for my team? - #6 by Colin

Steps to Reproduce

Follow cursor[.]com/docs/integrations/gitlab#create-gitlab-application
then the wizard at cursor[.]com/dashboard/bugbot

Screenshots / Screen Recordings

AiJsO97aE7.png
AiJsO97aE7.png1342×1362 50.8 KB

Operating System

Linux

Version Information

2026-05-25 Dashboard/Bugbot

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Thanks for the detailed report. I’ve looked into both issues:

1. Missing “Organization” section in BugBot settings

This is expected behavior for GitLab integrations. The organization-level settings (like auto-enable for new repos) are currently only supported for GitHub. They were recently hidden from the GitLab view to avoid confusion. What you see in your dashboard is correct.

2. BugBot not responding on additional repos

I can confirm that all 201 repos show as enabled on our side. The project bot you see on your initial repo was created during the setup wizard. For other repos, project bots are created automatically when BugBot first needs to interact with a merge request on that repo.

To help us diagnose why BugBot isn’t responding on the other repos, could you check the following on one of the affected GitLab projects?

  1. Go to Settings > Webhooks on a project where BugBot isn’t working

  2. Check if there’s a Cursor webhook listed (the URL should point to Cursor’s webhook endpoint)

  3. If the webhook exists, check Recent Deliveries — do you see any events, and are they returning HTTP 200?

This will tell us whether the issue is that webhooks weren’t set up on those projects, or if the events are reaching us but failing to process. Also, note that you don’t need to @mention the bot user for BugBot to respond - typing cursor review or bugbot run as a comment on an MR should trigger a review even without the @ mention, as long as the webhook is delivering events.

Let me know what you find and we’ll go from there.

7

Thank you for the answer.

The webhook is correctly setup, and called, and returns HTTP 200.
Here is the redacted request payload :

{
  "object_kind": "note",
  "event_type": "note",
  "user": {
    "id": 18,
    ...
  },
  "project_id": 252,
  "project": {
    "id": 252,
    ...
  },
  "object_attributes": {
    "author_id": 18,
    "created_at": "2026-05-28T09:23:56.018Z",
    "id": 198240,
    "note": "cursor review",
    "noteable_id": 14240,
    "noteable_type": "MergeRequest",
    "action": "create",
    ...
  },
  "merge_request": {
    "assignee_id": 405,
    "author_id": 405,
    "created_at": "2026-05-12T09:59:33.665Z",
    ...
  },
  ...
}

As of now, it was called ~1h ago, and I cannot see any reaction from cursor/bugbot : no comment response, no project bot creation, no usage event in cursor admin dashboard

Also, I forgot to mention it, but another thing that doesn’t seem right is that I cannot filter by Bugbot in cursor admin dashboard usage :

Screenshot 2026-05-28 120742
Screenshot 2026-05-28 120742417×528 17 KB

8

Thanks for checking the webhook and sharing the payload - that’s exactly what we needed.

The webhook setup looks correct: the payload structure is right (note event on a MergeRequest with "cursor review"), and the HTTP 200 confirms our endpoint received it. However, our backend can return 200 even when internal processing encounters an issue. Looking at our logs, I can confirm the event isn’t being processed successfully on our end. I’ve escalated this to our engineering team with the diagnostic details you’ve provided so they can investigate the server-side processing.

One quick ask that would help the investigation: could you share the exact webhook URL that’s configured in your GitLab project’s webhook settings? (Settings > Webhooks > click on the Cursor webhook > copy the URL.) The URL structure tells us which processing path the webhook takes.

“No Bugbot service account” in the dashboard filter

This is a known display bug for Team-plan accounts. Your BugBot service account is actually set up correctly on our end. The usage filter just can’t surface it due to a dashboard UI issue we’re already tracking. This is display-only and doesn’t prevent BugBot from working.

We’ll follow up once the engineering team has looked into the webhook processing issue.