GitHub Integration

Support Help
,
1

When using separate teams in Cursor is it the case that a Cursor GitHub App Installation ID can only be tied to one Cursor Team?

5

Hey @Steve_Nicholls, thanks for the question!

Yes, that’s correct today. A Cursor GitHub App installation is tied to a single Cursor team (the team that connected it). Since GitHub only allows one installation of a given app per GitHub org, that GitHub org’s connection effectively belongs to one Cursor team at a time. The reverse is fine though, one Cursor team can own connections to multiple GitHub orgs.

Better support for sharing one GitHub connection across multiple Cursor teams is actively being worked on.

8

Thanks for the response. So does that mean if we want to use the GitHub App for Cloud Agents we would have to put our 3000 users into one Team?

12

Hey @Steve_Nicholls, good question.

For a given GitHub org, effectively yes. Cloud Agents authorize repo access through the team’s GitHub connection, so everyone who wants to run Cloud Agents on repos in that GitHub org needs a seat on the Cursor team that owns that connection. A single team of that size is fully supported,/

Worth keeping in mind:

  1. The scoping is per GitHub org, not per company. If your repos are split across multiple GitHub orgs, each Cursor team can connect its own org and run Cloud Agents there independently. One team can also connect multiple GitHub orgs.

  2. Only features that use the team connection (Cloud Agents, Bugbot, Automations) are affected. Day to day Git access in the editor uses each developer’s own GitHub login, so members of other teams can still clone, push, and work normally.