Hi
I have integrated Slack to Github through Cursor. It works for me. However, if a non-github user of my company tries to use the Cursor app on Slack, the cloud agent rejects the request to github. Is there a way for me to allow that to happen?
The non-GitHub user may currently not have repository entitlement inside Cursor, even though team plan exists. Is there any alternative way for Cloud agent to talk to Github here?
Thanks
Venkatesh
I am trying to provide a way for my internal users (non engineering folks) to have the capability of understanding any logic in our codebase through this integration so that there is less dependency on such things from an engineer. Creating a pull request or trying to fix something in the code is out of scope for them. So ideally a read access to repo through Cursor agent.
indexed repo context is good for a start and we can manually sync the index time and again. What you are suggesting seems like a path forward, but wondering how do I go about this and try?
Hey there!
Cloud Agents require each user who triggers them (including via Slack) to have their own GitHub OAuth credentials connected in Cursor, since the agent acts on behalf of the triggering user’s identity. A cursor license is also required there.
That said, the newly released Cursor Agent SDK might make it much easier to build something that operates as an in-between layer. It’s built for custom integrations, bots, and similar use cases!
This approach would also work around users not having direct GitHub access, since GitHub access would instead be handled by the account authenticating to the agent.