Skip to main content

Command Palette

Search for a command to run...

Integrations

GitHub

The Cursor GitHub app connects your repositories so you can use features like Cloud Agents and Bugbot.

Setup

Requires Cursor admin access and GitHub org admin access.

  1. Go to Integrations in the dashboard
  2. Click Connect next to GitHub (or Manage Connections if already connected)
  3. Choose All repositories or Selected repositories
  4. Return to the dashboard to configure features on your repositories

To disconnect your GitHub account, return to the integrations dashboard and click Disconnect Account.

IP allow list configuration

If your organization uses GitHub's IP allow list feature to restrict access to your repositories, Cursor can be configured to use a hosted egress proxy with a narrow set of IPs.

The Cursor GitHub app has the IP list already pre-configured. You can enable the allowlist for installed apps to automatically inherit this list. This is the recommended approach, as it allows us to update the list and your organization receives updates automatically.

To enable this:

  1. Go to your organization's Security settings
  2. Navigate to IP allow list settings
  3. Check "Allow access by GitHub Apps"

For detailed instructions, see GitHub's documentation.

Add IPs directly to your allowlist

If your organization uses IdP-defined allowlists in GitHub or otherwise cannot use the pre-configured allowlist, add the proxy IPs listed in Git egress proxy and IP allow list.

Advanced networking

Self-hosted instances support multiple connection methods beyond IP whitelisting. For setup details and supported private networking options, see Private Connectivity.

Available for Enterprise customers. Use AWS PrivateLink when your GitHub Enterprise Server is in AWS or can sit behind an AWS Network Load Balancer. PrivateLink can cover Cursor accessing GHES and, when needed, GHES sending webhooks back to Cursor without public internet egress.

Best for: AWS-hosted GHES instances and teams that want private VPC endpoint connectivity

Security: HTTPS encryption, AWS PrivateLink, VPC endpoint policies, service account access tokens

Drawbacks: Requires coordination with Cursor and AWS endpoint service setup.

Available for Enterprise customers. Use Cloudflare Tunnel when AWS PrivateLink is not practical or when you need an outbound-only deployment model. Your network runs cloudflared, and Cursor provides the tunnel hostname and token.

Best for: Environments without inbound network access

Security: HTTPS encryption, Cloudflare Tunnel, service account access tokens

Drawbacks: Requires running and maintaining cloudflared in your environment.

Permissions

The GitHub app requests the following permissions to support Cursor features:

PermissionPurpose
Repository accessClone your code and create working branches
Pull requestsCreate PRs and leave review comments
IssuesTrack bugs and tasks discovered during reviews
Checks and statusesReport on code quality and test results
Actions and workflowsMonitor CI/CD pipelines and trigger CI re-runs from pull requests
AdministrationRead branch protection and required check rules to determine PR mergeability
Custom repository rolesDetermine user access levels so the correct merge and review options appear
Organization custom propertiesSurface organization-defined repository metadata in filtering

All permissions follow the principle of least privilege.

Protected Git Scopes

Lock your GitHub organization to your Cursor organization so only your teams can use its repositories with Cloud Agents, automations, and Bugbot. Protecting a scope requires GitHub organization owner or admin access. See Protected Git Scopes.

Troubleshooting

  • Install the GitHub app with repository access
  • Check repository permissions for private repos
  • Verify your GitHub account permissions

  • Grant the app write access to pull requests
  • Check branch protection rules
  • Reinstall if the app installation expired

  • Check if installed at organization level
  • Reinstall from github.com/apps/cursor
  • Contact support if installation is corrupted

Next steps

Once your GitHub integration is connected, configure the features that use it:

  • Bugbot — automated PR reviews that catch bugs and security issues
  • Cloud Agents — AI agents that run in the cloud on your repositories