Background Agents: Using a second github account, main github account is leaked in pull requests

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I have two github accounts. My cursor account is with my primary github login.
If I am using cursor with my second github account (and git is configured to my second account and cursor settings, github is also authorised to my second account), if I spin up a background agent to do a task, the resulting pull request will have commits authored by “cursoragent” and my primary account.
Thus linking my two accounts which is not what I want.
In the screenshot attached it should only refer to the second account.

Steps to Reproduce

Start a background agent in a repo on a second github account.

Expected Behavior

background agents should only operate in the context of the github account they are working in.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54 (user setup)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue