A user's Slack integration says it's not connected to GitHub, but it is

[IsaacAtAsh (Isaac Sukin)]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I have been setting up my PMs to use the Cursor Slack integration. So far it worked for 3 people, but the fourth is having issues. The three that worked were part of our GitHub org before accepting the Cursor invitation, so when they got the “Link Account” message in Slack they were able to connect their accounts and then @Cursor worked in Slack from there. But for the fourth, she clicked “Link Account” before accepting my invite to our GitHub org. Now she is part of the org, and has connected both Cursor and GitHub in her Cursor settings, but when she tries to get @Cursor to do something in Slack it replies:

You don’t seem to have write access to [redacted repo name]. Authorize the Cursor GitHub app if not installed, or make sure you have write access.
[Link Account]

She has write access, both from her org settings and explicitly in the repo.

Clicking “Link Account” opens a screen to authorize the Cursor app for our GitHub org - but it is already authorized. Trying to continue from that screen shows an error that only an admin can configure the app. Making her an admin doesn’t solve the problem either.

Attempting to use the Agents web UI will list the available repos but does not list any branches for her to pick from.

I tried deleting her account from Cursor and re-inviting her, but that didn’t change anything. We also waited 5 days and tried again to see if it is due to some caching issue, but that didn’t work either. My guess is there’s something internal on the Cursor side that needs to be reset. We reached out to Cursor support last week (the hi@ address) but haven’t gotten a response, so I’m posting here in the hope that it will get more visibility.

Steps to Reproduce

1. Invite a user to Cursor
2. That user posts a message to @Cursor in Slack and clicks “Link Account”
3. That user links Cursor to a GitHub account that does not have access to the relevant org
4. That user joins the org
5. That user attempts to get @Cursor to do something in Slack
6. Cursor replies saying the user must “Link Account”

Expected Behavior

At step 6, Cursor should have access to the org’s repos

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

n/a, Background Agent

Does this stop you from using Cursor

Yes - Cursor is unusable

[danperks (Dan)]

Hey Isaac, thanks for the report.

Can you confirm which user it is who is unable to use the Slack integration?
I’ve found your team, so the first name / prefix to the @ be fine!

I’ll ask the team to confirm what’s going on here, but most of the time, this is usually misconfiguration in GitHub that causes this!

[IsaacAtAsh (Isaac Sukin)]

Thanks - the affected user is Olivia.

Also including screenshots here of our GitHub configuration.

When she goes to https://cursor.com/dashboard?tab=integrations it shows both GitHub and Slack as connected.

[celia (Célia)]

same issue here. github org is helmlabs