Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
GitLab is connected in the Cursor dashboard. Cloud-native agents work when started on cursor.com/agents with a multi-repo Cloud Agent environment (primary private repo on gitlab.com under a group namespace, plus one dependency repo).
Local → cloud handoff from Agents Window does not work: start as This Computer, then Move to Cloud / Build in Cloud / Run in Cloud. UI sometimes shows misleading “connect GitHub” prompts despite GitLab repo.
Logs show StartBackgroundComposerFromSnapshot creates a bc-id, then within ~150ms calls fail with ERROR_NOT_FOUND / “Background composer not found” (cloudAgentStatus: 4). Cloud-native web agents stay connected (cloudAgentStatus: 2).
Also seen: GetRepositoryBranches → 401 Unauthorized or internal error on branch picker during handoff.
Steps to Reproduce
- Connect GitLab in dashboard; sync repos; configure multi-repo Cloud Agent environment (works on web)
- Open Agents Window (Cmd+Shift+P → Open Agents Window)
- Start local agent on This Computer for a private GitLab group project
- Move to Cloud / Build in Cloud / Run in Cloud
- Handoff fails
Control: Start as Cloud on cursor.com/agents → works.
Expected Behavior
Local Agents Window session should hand off to a running cloud VM with conversation context preserved.
Operating System
MacOS
Version Information
Cursor: 3.11.19 (Stable)
Layout: glass (Agents Window)
Additional Information
Host: gitlab.com, private group-namespace project, Owner/Maintainer permissions.
Setup: committed .cursor/environment.json (Dockerfile + install/start + repositoryDependencies).
API: StartBackgroundComposerFromSnapshot → immediate Background composer not found.
Happy to share Request ID/bc-id privately with support.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor