When a repository is selected and new cloud agent prompt is passed to it. It results in an error as shown on the screenshot.
This only happens for repository that is under a group/team on gitlab. It works when the repository is under my username.
I think the real issue is being masked here (which is something we should fix on our end).
Could you confirm two things?
Is your GitLab user a Maintainer or Owner on the project?
Does the project or group belong to a Premium or Ultimate plan (i.e., not Free)?
In the backend, we can see User does not have permission to create project access token, which usually means one of these two requirements isn’t being met.
Both of these are required for Cloud Agents to work on GitLab (docs). Let me know, and we can take it from there!
Cursor integrates with Gitlab via Project Access Tokens, which require a Premium or Ultimate subscription. This limitation might be different on personal projects.
I have just tried adding a service account to a group that owns the project, and it was added successfully. The same with the token for the SA with read/write permissions for repos. Maybe that is a solution to cursor integration for group projects?
