We're having trouble granting cursor agents access to our github org

Support Help
, , ,
1

Hi!

Our team is excited to try the slack cursor agent, but unfortunately we’re having trouble authorizing the cursor app in github. If we go to Organizations > Github Apps then we can see that cursor has all repositories already setup with full access. Unfortunately though cursor only seems to be able to detect 1 of our repos and cant see all of them and we’re not sure why.

image
image1924×1366 207 KB

If we go to Organizations > Third-party application access policy then we see Policy: Access restricted but we don’t see any line for cursor with approved or denied on that page on the table.

When another developer in our org tries to link cursor on their account they get directed to github to “update cursor’s repository access” but are only given the option to select some repos and from that list they are only allowed to “request” access to them.

But unfortunately if they try to request access they get this error:

image
image767×376 4.39 KB

even though this permission in our org is on:

image
image1286×636 50.9 KB

I was wondering if we’re doing something wrong or if anyone knows what we have to do to grant all of our developers access to use cursor in all of our repos?

Thank you!

3

Hey there!

Thanks for reaching out. Your GitHub App installation looks correct (all repositories selected, permissions look right). The problem seems to be on the OAuth App side.

There are two separate GitHub integrations at play:

  1. GitHub App (shown as “Cursor” under your org’s GitHub Apps settings)

    • Used for Cloud Agents and Bugbot server-side

    • Your screenshot confirms this is set up correctly.

  2. OAuth App (shown as “Cursor GitHub Extension”)

    • This is the user-level connection each developer authorizes individually

    • Because your org has a restricted third-party access policy, this OAuth App must be approved by an org owner first.

    • That’s why developers are seeing: “This action must be performed by an organization owner.” They’re being redirected to a flow that requires org-owner permissions.

Fix: org owner grants OAuth access

A GitHub org owner should:

  1. Go to github.com/settings/applications (their personal GitHub settings)

  2. Find “Cursor GitHub Extension” and open it

  3. Under Organization access, click Grant next to your org

Once granted, Cursor should show up in your org’s approved third-party applications, and other developers should be able to connect their GitHub accounts without hitting that error.

About “only detects 1 repo” -

This typically resolves automatically once the OAuth App is approved at the org level. If it doesn’t:

  • have the affected user disconnect and reconnect GitHub in Cursor’s Integrations page, and

  • make sure all repositories are selected during reconnect.

Let me know if granting org access clears it up, or if you run into any other issues.

Best,
Mohit