At https://cursor.com/onboard I’m trying to set up a new environment, but the associated GitLab repositories are not loading. There are no options to select from to onboard and set up a new environment.
Steps to Reproduce
I don’t know if it will work for everyone, but go to https://cursor.com/onboard with a linked GitLab account and you should see no options. The “Add Repositories” seems to work fine, and the refresh starts, but then no repos are found still.
Expected Behavior
There used to be a long list of repositories that were available to select from. Now there aren’t any.
Org size, roughly how many projects are in the group or org you’re trying to connect? Especially if it’s over about 50 or over about 1 000 repos.
Your GitLab role, Owner or Maintainer, or Developer, Reporter, Guest?
DevTools Network tab: open cursor.com/onboard, press F12 then Network, reload the page. Do you see any requests that hang for about 60 seconds and then end with 504, or another error? If yes, send the name or URL of the request and the status.
Have you tried disconnecting and reconnecting the GitLab integration in https://cursor.com/dashboard → Integrations? Sometimes that recreates the link and the list loads again.
With that info I can tell if this is a known bug and which one, or something new.
Hard to get a precise number, but I’d estimate around 300 projects in our org.
Role is different per project/group. I’m Developer on most, but Maintainer on some (mostly the ones I care about).
Actually there’s this call that hung for a while (30sec?) but eventually finished (see screenshot). Notably the final payload DID seem to have our repos listed, but the UI didn’t populate with them still.
Yeah, I tried disconnecting and reconnecting the integration - no diff.
Thanks for the update. Looks like the original issue with the empty dropdown is fixed now. The Failed to get service account access token error during Start Agent is a separate issue, and it’s related to how Cloud Agent gets GitLab creds for a specific repo.
To match this to an existing ticket or file a new one, we’ll need a few details:
Rough time with timezone when you last reproduced it. This helps us find backend logs.
DevTools > Network: open the modal, click Start Agent, find the failed request, probably something like start-agent or create-environment or provision. Please share the request URL, status code, and the response payload. It should include a request ID or trace ID.
Do you see perception/data-hub in the list of projects connected to the Cursor GitLab integration? You can check in GitLab at Settings > Applications, or ask the group owner. There should be a Cursor authorization with an explicit project list.
Does this happen on any repo, or only on perception/data-hub? If you’ve got a smaller GitLab repo, please try Start Agent there too and tell us if it reproduces.
Also, to avoid mixing two different bugs in one thread since the dropdown issue is basically closed now, can you create a separate post titled something like service account access token error when starting agent? Share the link here and I’ll pick it up.
I attached the failing network call screenshot. Just reproduced it now at 9:03am MST.
Let’s not create a new thread - the main issue is I can’t make a cloud environment. That still holds, despite the UI changes you guys are launching past couple of days.
Thanks for the network request screenshot, that’s exactly what we need. A 401 on startBackgroundComposerFromSnapshot with the message “Failed to get service account access token” is a known issue where the backend can’t create a project access token in GitLab to start the Cloud Agent. Even though the error code says GITHUB, this is the GitLab path.
Most commonly, the cause is one of these:
Your GitLab role is below Maintainer on that specific project. In GitLab, project access tokens can only be created if you’re Maintainer or Owner. You mentioned you’re Developer on most projects, so if perception/data-hub is one of those, that would fully explain the 401.
Your group’s GitLab plan. On GitLab Free, project access tokens are restricted for private groups. Premium or Ultimate works.
Less often, an expired or revoked token for all users linked to the integration.
To confirm, and to open or update a ticket if needed:
Check your role specifically on perception/data-hub GitLab > project > Members. You need Maintainer or Owner.
If you have a smaller project where you’re Maintainer or Owner, try starting the Agent there. If it works there, it’s a role issue.
From that same 401 request in DevTools, please share the full response body payload. It should include error and details. If you can, also include the x-request-id or x-amzn-trace-id header. That helps us find the request in the logs.
Okay, I was able to confirm that a lack of Maintainer role was the issue here. I was only Developer, and after getting elevated permissions this now works.
