I connected both my GitHub and GitLab repositories to my Cursor account. However, I had already noticed that the GitLab integration seems less robust compared to GitHub.
Now that automations are available, I tried adding them to my GitLab repositories with a trigger configured to run when a pull request is opened. After setting everything up, nothing happened when a PR was created.
I would like to understand whether the automation feature currently supports GitLab triggers properly, or if there is a way to verify whether the integration is working. Is there any place where I can check logs or debug why the automation is not being triggered?
Steps to Reproduce
1. Connect a GitLab repository to the Cursor account.
2. Create a new automation.
3. Configure the trigger to run when a PR (merge request) is opened.
4. Add the GitLab repository to the automation.
5. Open a new PR/Merge Request in the repository.
Expected Behavior
When a PR/Merge Request is opened in the GitLab repository, the configured automation should run automatically.
I tried to create an automation with gitlab but I got the following error:
Repository access denied
The automation could not authenticate with the repository. Verify the GitHub App is installed for this repo and that the required permissions are granted.
When trying to do a test execution (or any actual execution) of automations I am getting this unauthenticated error: Failed to start background composer: [unauthenticated] Error.
When I go into run history is appears to be a github authentication issue, but we are using Gitlab not Github. Cloud Agents work correctly and connect to Gitlab, is this a specific Gitlab/Automations issue?
“Repository access denied
The automation could not authenticate with the repository. Verify the GitHub App is installed for this repo and that the required permissions are granted.”
Steps to Reproduce
Have a gitlab repository configured for cloud agents with no github integration configured
Go to automations in the Cursor web app
Click one of the pre-built automations like the slack digest reminder automation, run a test of the automation
Expected Behavior
Gitlab configured projects should successfully launch automations like Cloud Agents.
Thanks for flagging this! I ran into the same thing last night and reported it as a bug to the team. I’ve attached your report and will update here when there’s progress.
HTTP 400 {"success":false,"error":"Failed to start background composer: [unauthenticated] Error"}
then in the run history we see
Trigger · 10 Mar 2026, 10:32 am
Webhook event
Repository access denied
The automation could not authenticate with the repository. Verify the GitHub App is installed for this repo and that the required permissions are granted.
Reconnect GitHub
It was a direct email support ticket - the team informed they have logged an issue on their roadmap and they want to introduce but no ETA and it’s high on their list!
I asked them to perhaps give me the link then I can post it here, and/or even respond here directly with more info!
With that said, configuring automations with webhook/cron triggers is still facing the earlier-mentioned bug ([unauthenticated] or Repository access denied errors).
This is a known issue, and we’re tracking it internally. Will follow up here when there’s progress!
