Cloud Agents fail intermittently for GitLab group project (invalid_token, branch not found, gitlab rate limit issues)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Intermittent GitLab Cloud Agent failures on GitLab’s group repo — “invalid_token”, “development branch not found” and “GitLab is rate limiting requests”

Steps to Reproduce

Basically I have developed a automation workflow where JIRA, cursor and GitLab are connected and the cursor cloud agent APIs are used when a condition is matched on JIRA.

Steps to Reproduce

Prerequisites

  • GitLab account with Maintainer access on dgs-dev/clearsite/clearsite-core
  • dgs-dev group is on GitLab Premium
  • Cursor account with GitLab integration connected (Dashboard → Integrations → GitLab)

Setup (one-time)

  1. Open integrations in cursor web dashboard
  2. Connect GitLab and complete OAuth authorization
  3. Click Manage next to GitLab → Sync Repos
  4. Confirm dgs-dev/clearsite/clearsite-core appears in the repo list

Reproduce the failure
5. Open Cloud Agents:

  1. Select repository: gitlab.com/dgs-dev/clearsite/clearsite-core
  2. Select branch: development
  3. Enter any prompt (e.g. “List files in the repo root”) and start the agent
  4. Observe the result:
    • Sometimes fails immediately with invalid_token (401)
    • Sometimes fails with development branch not found (400)
    • Sometimes GitLab is rate limiting requests (429)
    • Sometimes agent starts successfully (intermittent)

Additional observation
10. In GitLab → Project → Settings → Access Tokens, a new Cursor project access token is auto-created (Developer role) when the agent attempts git access
11. Re-run steps 5–8 multiple times without changing configuration — errors vary between attempts

Expected Behavior

Per Cursor GitLab documentation, Cloud Agents should work with GitLab repositories when:

  • The group is on a paid GitLab plan (Premium/Ultimate)
  • The connecting user has Maintainer access for initial setup
  • GitLab is connected in Cursor Integrations and repositories are synced

When we start a Cloud Agent on dgs-dev/clearsite/clearsite-core and select branch development, we expect:

  • The agent launch to succeed every time (not intermittently)
  • Branch development to be found and used (it exists on the remote)
  • No misleading errors such as invalid_token, development branch not found, or GitHub-related error messages
  • Cursor to use a valid project access token for git read/write operations
  • The agent to run to completion or fail with a clear, accurate error if something is genuinely misconfigured

Screenshots / Screen Recordings

1.png
1.png742×283 17.3 KB
2.png
2.png757×335 20 KB
3.png
3.png705×234 18 KB

Operating System

Windows 10/11

Version Information

Launch path: Cursor Web UI (https://cursor.com/agents)

Additional Information

  • Intermittent failures: same steps produce different errors (invalid_token vs development branch not found vs GitLab is rate limiting requests)
  • Branch development exists on GitLab remote (not a missing branch issue)
  • dgs-dev group is on GitLab Premium; integration user is Maintainer on group/subgroup/project

Does this stop you from using Cursor

No - Cursor works, but with this issue