a PR created by cloud agent (not automation) is currently attributed to me. i’d like it to be attributed to cursor or cursor[bot] or whatever, but not myself. comments are already submitted like this, i don’t understand why PRs are not.
i found the thread in this forum discussing this matter, but that was about PR created by automations, not cloud agents (apparently there’s a difference?).
extensive research points at GitHub Cursor app (account-wide) vs something called “personal Oauth token”, but i can’t figure out the difference nor how to configure which one will be used when and where. please advise.
Hey, thanks for the request. There are two different GitHub identities in play, and they’re used for different jobs:
Cursor GitHub App install at the account or org level gives Cursor access to repos. It’s used for push tokens, PR comments, Bugbot, and Automations. Anything done through it shows up as cursor[bot].
Personal GitHub connection via OAuth is your GitHub account connected in Cursor. It’s used when Cursor acts on your behalf. Creating a PR via the interactive Cloud Agent uses this, so the PR author is you.
This is intentional. A PR opened by an agent you started is attributed to you for ownership and review governance. If the PR were authorized by the bot, you could approve your own PR, and a few teams flagged that as an issue. The commits still show as Cursor Agent [email protected] with you as co-author.
The difference you noticed is that Automations run under the GitHub App identity, so their PRs come from the app. Interactive Cloud Agent runs do not.
There’s no UI toggle to change this for interactive runs right now. By default, app identity is used for agents started via a service account API key or via Automations. If you need PRs to come from the Cursor app, that’s the right path.
I get that you’d want this to be configurable by default. I’ll pass this to the team as a request for an opt-in toggle. Let me know if you want help setting up runs via a service account or Automations.