Creating a cloud agent fails because it cannot connect to github, but github is connected

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I create a new agent with the Cursor IDE and setting it from Local => Cloud it fails on github issues.

It says Github/Gitlab access required; Failed to check Github/Gitlab access.

Pressing the setup button, it takes you to the cursor dashboard, it says Github is connected.

I have personall reconnected & disconnected the github account, my CTO has also. Github is supposed to be connected, but it’s not working.

Steps to Reproduce

Login with my account ( jake @ socket.dev )
Try to create a new agent in the cursor IDE setting it as cloud.
It can’t start or run due to github access being not connected.

Expected Behavior

Cloud agent’s should work and start and be able to connect to github.

Operating System

MacOS

Version Information

Version: 2.6.19 (Universal)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 23.6.0

Additional Information

  • We migrated from github teams based billing for Socket · GitHub to github cloud enterprise. I feel like this change might have poisoned everything and disconnecting and reconnecting is not helping.

I imagine something is poisoned and I don’t know what or why.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. The migration from GitHub Teams to GitHub Cloud Enterprise likely caused the issue here. When the org plan changes on GitHub’s side, the Cursor GitHub App installation can become stale on our backend, and reconnecting through the dashboard doesn’t always fix it.

The team is aware of this type of issue. To help investigate your specific case, could you share:

  • Any errors in DevTools. Go to Help, then Toggle Developer Tools, then open the Console tab, and try switching to Cloud agent

Also worth trying: go to your GitHub org settings at Sign in to GitHub · GitHub, find the Cursor GitHub App, uninstall it completely, then reinstall it from https://cursor.com/dashboard?tab=integrations. This might refresh the installation ID on our end.

If that doesn’t help, we may need to manually clear the cached state for your org on the backend. Let me know how it goes.

4

We ddi try to already uninstall the github app completely for cursor from the Socket organization.

And that did not help, all the most nuclear options for getting github reconnected with cursor didnt work.

I’d need someone on your team to manually clear all the cached state for our org so we can try to reconnect it again.

5

For context, for some reason a cloud agent spawned from the website interface does work. but a cloud agent spawned from my cursor IDE does not.

Also half the automations are running and the other half can’t connect to github.

Like it’s in some kind of zalgo/zombie state where it works sometimes but fails other times.

6

If you could manually clear the cached state for our org that would really help.

7

Actually it was the git alias, removing the git alias allowed it to resolve the remote github project from my local project.

Now it errors out instead on wanting github enterprise details when its not self hosted enterprise, it’s hosted on github.com

8

Good that you figured out the git alias part.

For the new error asking for GitHub Enterprise details, we’ve seen a similar bug where the Cloud Agent URL parser incorrectly treats certain repos as self-hosted enterprise instances. Could you share:

  1. The exact error message you’re seeing now
  2. What your git remote URL looks like (git remote -v output)

This will help us confirm whether it’s the same type of parsing bug or something specific to GitHub Cloud Enterprise detection.

9

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.