Running into this error when trying to creating a project from cursor. Agents works fine, committing and pushing as well. Just unable to create a project with the repo.
Describe the Bug
Running into an error when trying to creating a project from cursor. Agents works fine, committing and pushing as well. Just unable to create a project with the repo.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
Add a new project…
Choose a repo
Create project
Expected Behavior
What is meant to happen here that isn’t working correctly?
Expected to create a project
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
That message means Cursor’s own GitLab connection doesn’t currently see that repository. Committing and pushing still work because they use your local git credentials, but creating a project (and cloud agents in general) needs the repo to be connected through Cursor. Could you try these steps?
Open cursor.com and go to Dashboard, then Integrations.
Under GitLab, click Connect if it isn’t connected yet, and sign in with the GitLab account that has access to this repository.
Once connected, click “Sync Repos” on the GitLab card and give it a couple of minutes.
Check your role on the project in GitLab (Project, then Manage, then Members). It needs to be Maintainer or Owner for the sync to pick it up. If you only have Developer access, ask a project owner to bump you up, or have them connect GitLab from their side.
Open cursor.com/agents, click the repository picker and search for the repo. If it shows up there, go back to Cursor and try Create Project again.
Hi, I’ve been having this problem since Projects launched.
I am the GitLab owner of all repositories. Most of my repos are in GitLab groups.
You suggested, “5. Open cursor.com/agents, click the repository picker and search for the repo. If it shows up there, go back to Cursor and try Create Project again.” What do you mean by the repository picker? The web interface is quite different to the local Cursor interface.
Even so, when I click Sync Repos and wait, it doesn’t fix the issue.
Do I need a paid GitLab subscription for this to work with Cursor?
To work on a GitLab.com repo in the cloud (Projects and cloud agents), Cursor creates a project access token for that repo, and GitLab.com only allows project access tokens on the Premium or Ultimate plans. On the Free plan GitLab refuses to create one for every role, Owner included, so Create Project fails even though everything else looks connected.
So to answer your question: yes, for repos hosted on GitLab.com, the group that owns the repo needs to be on GitLab Premium or Ultimate. This is listed in our GitLab integration docs: GitLab | Cursor Docs
