Where does the bug appear (feature/product)?
Cloud Agent (GitHub, Slack, Web, Linear)
Describe the Bug
A GitHub Enterprise Server integration cannot be used by a newly created Cursor team.
The GitHub Enterprise app is configured at the organization level and is available to the existing/default team, but the same GitHub Enterprise instance cannot be configured or used from another team in the organization.
Although repositories from the GitHub Enterprise instance are visible when creating an Environment for the new team, creating the Environment fails because Cursor reports that the GitHub Enterprise instance is not configured for that team.
Steps to Reproduce
- Create a Cursor organization.
- Create an initial team in the organization.
- Configure a GitHub Enterprise Server integration for a GHES instance (e.g.
github.example.ghe.com). - Verify that the GHES integration works for the initial team.
- Create a second team in the same Cursor organization.
- Go to the second team’s Integrations & MCP settings.
- Open the GitHub Enterprise integration.
- The configured GHES instance is not available for selection and the integration shows “No apps”.
- Go to the second team’s Cloud Agents and attempt to create a Cloud Agent. Repositories from the GHES instance cannot be selected.
- Go to the second team’s Environments and create a new Environment.
- The repositories from the GHES instance are visible and can be selected.
- Attempt to create the Environment.
- Environment creation fails with HTTP 400 and the following error:
Git enterprise instance not found for hostname: github.example.ghe.com. Please set up the enterprise instance in Settings.
Please note that we’ve also tried to delete and re-add the GHES integration to our newly created team, but doing so always only displays it in the original team, and makes it available for use there. Never in our newly created team.
Expected Behavior
A GitHub Enterprise Server instance configured for a Cursor organization should be usable by any team that has been granted access to that integration.
The second team should be able to:
- Configure/select the existing GitHub Enterprise integration.
- Select repositories from the GitHub Enterprise instance for Cloud Agents.
- Create Environments using repositories from that GitHub Enterprise instance.
If GitHub Enterprise integrations are intentionally team-scoped, there should be a way for an organization administrator to explicitly assign the existing GHES instance to another team.
Operating System
Other
Version Information
Cursor configuration in the Browser
Additional Information
The behavior appears inconsistent across the UI:
- The GHES application exists and is visible under the organization’s app management.
- The GHES integration works correctly for the original team.
- In the new team’s integration settings, GitHub Enterprise shows “No apps” even though the application exists.
- When creating an Environment in the new team, repositories from the GHES instance are nevertheless visible and selectable.
- The failure occurs only when the Environment is actually created.
The resulting error specifically states that the GitHub Enterprise instance cannot be found for the hostname and instructs the user to configure it in Settings, even though the instance is already configured at the organization level and works for another team.
This suggests that the GHES instance configuration/registration is not being correctly resolved in the context of the new team’s Environment/Cloud Agent backend.
The issue is reproducible with a newly created team within the same Cursor organization.
Does this stop you from using Cursor
Yes - Cursor is unusable