[Bug] Solo Ultra Account: Integrations throw ERROR_USER_NOT_FOUND (get-github-installations 404)

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I am on a solo Ultra Plan account (gregbarajas). When attempting to link my GitHub account via [cursor > dashboard > integrations) to use Cloud Agents, the integration fails to load.

The dashboard displays “Failed to load GitHub settings” and gets stuck on a “Connect” button loop.

Steps to Reproduce

Log into [cursor > dashboard integrations] on a solo Ultra account.

Click Connect on the GitHub integration line.

Complete the OAuth installation on GitHub for an organization (kilograms).

Return to the Cursor dashboard.

Expected Behavior

The GitHub organization repositories load into the Cloud Agents dropdown menu.

Operating System

Windows 10/11

Version Information

Web Dashboard / cursor.com

Additional Information

Actual Behavior:
The integrations page displays “Failed to load GitHub settings”. Checking Developer Tools shows the request POST https://cursor.com/api/dashboard/get-github-installations failing with a 404 Not Found and returning the following payload:
{
“error”: {
“message”: “Error”,
“details”: [
{
“error”: “ERROR_USER_NOT_FOUND”,
“details”: [
{
“title”: “User not found.”,
“detail”: “User not found in team”
}
]
}
]
}
}

It appears the backend endpoint get-github-installations is attempting to validate my account against a team membership table (User not found in team) rather than my solo profile, locking the OAuth integration state. Please flush the stale integration/installation record for my account.
“”"

file_path = “cursor_bug_report.md”
with open(file_path, “w”, encoding=“utf-8”) as f:
f.write(markdown_content)

print(f"File created: {file_path}")

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Greg_Barajas, thanks for the detailed report.

Your read of the failing request is right, and your account itself is in good standing. The request that loads your GitHub settings is failing on our side while it processes an installation record tied to an old, inactive team, and that stops the whole page from loading.

This is a known issue we’re already tracking, and I’ve added your report to it. There’s no action needed on your end (uninstalling and reinstalling the GitHub app won’t clear it, so no need to keep retrying that). We’ll follow up here once the fix is out.