This is a follow up to this thread that was closed with no acknowledgement for some reason: GitLab integration support We were very excited to try Cloud Agents but were disappointed because right now the integration with Gitlab feels very rough, the onboarding process doesn’t work because it checks…

The previous thread was auto-closed as there had been no activity in the last one month, and that shouldn’t have happened. I apologize for that. On the Maintainer requirement: we recently shipped a fix so that Developer-level GitLab users can now see and select repos in the repo picker (previously,…

[image] Mohit: The concerns about per-user service account creation and bot proliferation are valid and something I’ve heard from multiple teams. Is there an issue we can track to monitor progress on this? Our company is using legacy privacy mode due to this issue and this keeps us from doing…

Just want to chime in - agree on two issues: Maintainer access requirement for env setup is too much. I ran into this issue here and had a whole different thread about it trying to figure out the problem ( Cursor onboard not showing repositories ). At the very least the error message should be a …

With the recent update to environments the Gitlab integration seems to have been fixed and I can now use Cloud agents with a Developer level access!

I literally just tried it this morning a few hours ago and couldn’t until I was given Maintainer permissions :thinking: To clarify - you can USE cloud agents with Developer access, but you can’t init/create the environment initially without Maintainer (from what my testing/experience showed this mo…

@raphael-yapla can you confirm you can CREATE a Gitlab environment for a new repo with only Developer role? If so, maybe they changed something in past hours or else there is something strange going on.

Oh very interesting! Thanks for trying it again - I’ll attempt it as well again and see if results are any different from yesterday morning.

Nope, still same failure for me on a repo where I am only Developer: Failed to get service account access token: Failed to get service account access token for any user.

Gitlab integration requires unreasonable access for teams

Ideas Feedback

raphael-yapla (Raphael A.) May 15, 2026, 2:52pm 10

Yes with single repos no problem, I can create the environment with a Developer role straight from the website.

With multi-repo it just doesn’t work but I don’t know that it’s related to Gitlab, I created a separate topic for this.

Topic		Replies	Views
Cursor onboard not showing repositories Bug Reports cloud-agents , gitlab , linear-linked	8	120	May 14, 2026
GitLab integration support Feature Requests teams-enterprise , cloud-agents , gitlab	4	521	March 13, 2026
Can't setup a multi-repo Cloud Agent environment Bug Reports cloud-agents , gitlab , linear-linked	4	107	June 16, 2026
Cursor should completely change the process for connecting to GitLab to fit the scope of the integration Feature Requests security , cloud-agents , gitlab	0	49	May 17, 2026
Pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest) Bug Reports cloud-agents , github , linear , linear-linked	9	387	April 12, 2026

Gitlab integration requires unreasonable access for teams

Related topics