I have successfully connected my GitLab account to the Cursor dashboard under Integrations & MCP. The UI correctly displays “Connected as ‘natanel.dvir’”. However, when I click “Manage” and then “Sync repositories”, a toast message appears stating “Repository sync started. This may take a few minutes”, but the repositories never actually populate.
Because the repositories are failing to sync, I am completely blocked from using Cloud Agents/Automations. When I try to run an automation, I receive the error: “You need to connect your SCM account to Cursor to access a repository in the selected automation environment.”
Steps to Reproduce
Steps to Reproduce
Navigate to the Cursor Dashboard → Integrations & MCP.
Observe the toast notification: “Repository sync started. This may take a few minutes.”
Wait indefinitely. No repositories are listed.
Attempt to trigger a Cloud Agent automation.
Observe the SCM connection error.
Expected Behavior
After the sync toast appears, the dashboard should successfully display my available GitLab repositories, allowing me to select them for Cloud Agents and automations.
On our side we can see a No valid access tokens available after refresh attempts warning in the logs, indicating the GitLab OAuth token cannot be refreshed,. Could you try disconnecting and reconnecting the Gitlab integration?
This looks likes the same issue reported here, which I am still able to reproduce.
I’ve added your report to the ticket we’re tracking this issue on! Unfortunately, multi-repo automations won’t be available to you until this is fixed. I’ll update you when that’s the case!
Selecting a single repository while configuring an automation, rather than multiple.
Are you trying to set up a multi-repo automation (all repos cloned down to the Cloud Agent on every run), or trying to configure an automation that will run when a certain action happens on any given repo (but only needs the context on one repo)?
The second option -
Configure an automation that will run once found certain output -
For example - some repeating error found, and its relevant for a specific repo, then I’d expect the next step would be investigating that repo.
In some cases we would need multi-repo context - thats why I would need to simply have all of them in context.
@Colin
Now once I’ve set a single repo, Added the Gitlab mcp, I immediately get the 429 error.
And when trying to run the automation I’m getting
“Failed to start background composer:
[unauthenticated] Error”
Putting the GitLab MCP aside for a moment (happy to come back to it), I dug into the backend and found that your automation has some malformed data stored for the repo, which looks like is what’s causing the failures.
As a quick test, could you try creating a brand-new automation and selecting the same repo?
Likely, the creation will fail, but you should be able to click into the Cloud Agent that is breifly created an extract a bc- ID from the URL.
Could you do that and share the ID with me?
We definitely have lots of Automations targeting Gitlab repos, so I suspect that there’s just something odd in the configuration (or a corner case bug) that’s impacting your ability to use these repos. We’ll get to the bottom of it.
I wouldn’t expect anything to update on that page after the repo sync is done. What happens over here now?
