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, only Maintainers could see them). However, the initial setup — creating the project access token and webhook on a repo — still requires Maintainer access, which is a constraint of GitLab’s API for project access tokens.
The concerns about per-user service account creation and bot proliferation are valid and something I’ve heard from multiple teams. A team-level service account model (one configured bot for the whole Cursor team, rather than tokens created per-user per-repo) would make this much more practical for production use. That feedback is noted and helps our team understand what’s needed for GitLab teams at scale.
For the separate issue where Cloud Agent creation fails with a GitHub credentials check — that’s tracked in the main GitLab Cloud Agent thread and our team is working through the remaining integration gaps.