cursor automation creates pr as “cursor” instead of as user when automation is private. docs say opposite
Hey, thanks for the report. This behavior is expected. PR attribution is currently decided not by the automation scope, but by which GitHub token is available when the PR is created. If the repo is connected via the Cursor GitHub App and your personal GitHub OAuth isn’t linked to your account, the PR is created using the installation token and shows up as cursor[bot], even for Private user-scoped automations.
Workaround to make PRs come from you: make sure your account settings have personal GitHub OAuth connected, not just the GitHub App connected at the repo level. After that, user-scoped automations should use your token.
Configurable PR attribution for automations is already in the backlog, but I can’t share an ETA yet.
Also, can you tell me which exact line in the docs you’re referring to where the docs say the opposite. Please share a link or a quote. If it’s wrong, we’ll fix it.
Private automations open pull requests as your GitHub account.
how do i do this?
You can connect personal GitHub OAuth like this: open https://cursor.com/dashboard, go to Integrations → GitHub, and complete the OAuth flow sign in with GitHub. This is separate from the GitHub App that’s installed on the repo, you need both. The App gives Cursor access to the code, and personal OAuth is used to attribute PRs to you.
After you connect it, try recreating the Private automation and confirm the PR now opens from your GitHub account.
And thanks for the exact quote from the docs. You’re right, the wording in the identity section is misleading. I’ll pass this to the docs team to fix. Current behavior depends on which token is available when the PR is created. Personal OAuth means it’s opened by you, otherwise it falls back to the installation token and shows up as cursor[bot].