Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
I’m asking for an update on this issue that was automatically closed: Repository doesn't show up in list
My company has hundreds of repos on Gitlab. As is, the cloud agent feature is unusable 90% of the time because I can only select a random selection of repositories, and not the ones I actually work in.
@Deanrie - can you share what is the Gitlab issue you were blocked on. I searched the gitlab project and only found this which was completed in 2025: list repository tree api returns page number instead of using keyset pagination as documented (#427205) · Issues · GitLab.org / GitLab · GitLab
Steps to Reproduce
- Launch an agent in Slack.
- Hit Switch repository.
- Most repos aren’t available in the repo selection list.
Expected Behavior
All repos under my top level company group are shown.
Operating System
MacOS
Version Information
Version: 3.7.36
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
This is a confirmed, known issue, and it’s the same root cause as the thread you linked. For GitLab orgs with a lot of repos, the repo picker (both on cursor.com/agents and the Switch repository dropdown in Slack) loads only a partial list, so the repo you want often isn’t shown.
To answer your question directly: this isn’t a GitLab API bug you’re waiting on. The limitation is on our side in how we list repos for very large GitLab orgs, and the Slack picker is more constrained than the web one. We’ve been shipping improvements for large orgs, but they roll out gradually and may not have reached your account yet.
The reliable way to unblock yourself in Slack today is to skip the picker and name the repo directly in your message:
@Cursor repo=owner/repo <your prompt> — for a GitLab subgroup, use repo=group/subgroup/repo. When the repo is in your message, Cursor doesn’t load the full list and starts right away.- Set a default so you don’t repeat it each time: run
@Cursor settings for your personal default repo, or set a channel default repository.
- You can also launch the agent from the Cursor IDE, which targets the current repo directly and skips the picker.
One quick check: the picker only surfaces repos where you have Developer access or higher in GitLab - so if a specific repo is still missing after the steps above, confirm your access level on it.
Give the repo= approach a try; that should get you running on the repos you need right now while we keep improving the picker for large orgs.