My organization has a very large GitLab namespace with hundreds of repositories across nested groups. When creating a new Cursor Automation, I cannot find the repo I work in because the repository picker does not surface it — either there is no effective search/filter, or only a partial subset of repos is loaded.
This blocks setting up automations for repos that are not in the loaded subset.
Steps to Reproduce
Connect GitLab account in Cursor dashboard → Integrations (confirmed connected)
Go to https://cursor.com/automations
Click New to create a new automation
Add a Git trigger (e.g. Pull Request → Opened) or set a repository for the automation
Open the Select repo dropdown / repository picker
Search or scroll for a known repo you have Developer+ access to
Expected Behavior
I can search or filter the repo list and select my target repo, or manually enter the full GitLab path (including nested groups).
Hi @Hasan_Salim_Kanmaz Thank you for raising this. This is a known limitation with the Automations repository picker for large GitLab organizations. When there are hundreds of repos across nested groups, the picker often only loads a partial list, so some projects never appear even if GitLab is connected and you have access.
We are actively working on improvements so large GitLab namespaces can search and select repos reliably without loading the full list. In the meantime, try Sync repositories under Dashboard → Integrations → GitLab, then use Refresh in the Automations picker and search by the full path (for example group/subgroup/repo). Also, confirm you have Developer access or higher on that project in GitLab. If a teammate can already see the repo in the picker, they may be able to create the automation for that repo while we continue improving this.
Sorry for the friction, and thanks for bearing with us while we get this into better shape.
I tried your suggestion but it didn’t work. Unfortunately, I am blocked and I can’t create any automation for our repo. Actually, I am experiencing this issue for a while. Do you have a clear roadmap/estimate regarding when you plan to fix this?