Background Agent (GitHub, Slack, Linear,…)
Currently, disabling cursor as a co-author is not supported in cloud agent, only in local development.
The request here is to add a setting to disable cursor as a co-author in all places, cloud-agents specifically
Thanks!
Would love to see a configuration added for this too
I want this for Cursor CLI
Remove the trailer from git commits
Background Agent (GitHub, Slack, Web, Linear)
Cannot disable commit attribution on cloud agent commits.
Execute a task using a cursor cloud instance.
Windows 10/11
Cursor Cloud Agents
No - Cursor works, but with this issue
Commit Attribution is OFF in Cursor Settings → Agents → Attribution, but the agent still adds Co-authored-by: Cursor <[email protected]> to every commit. This should be fully disableable on all commit paths (IDE, CLI, cloud).
Commit Attribution is OFF in Cursor Settings → Agents → Attribution, but the agent still adds Co-authored-by: Cursor <[email protected]> to every commit.
Same as previous user. +1 for disable feature.
Would really appreciate a way to turn off cursoragent as my PR author. I find it obnoxious spam from the coding tools that they try to insert themselves as the commit authors. I don’t care if my teammates are using Claude or Cursor or any other tool - the human is the author and the human is the one responsible for the code change. Please allow us to disable cursor cloud agent attribution.
My main concern is that this misrepresents ownership of the change. I am still the person responsible for reviewing, approving, and shipping the code. Cursor is a tool I use to produce the change, not the party accountable for it.
A few other concerns:
git blame points to Cursor instead of the engineer responsible for the change.
Contribution stats and internal engineering metrics can become inaccurate.
A lot of tooling only looks at the primary author and ignores Co-authored-by.
Incident investigation and ownership tracking become harder later.
It can also mess with compliance and audit trails where the Git author is expected to identify the person responsible for a change.
How might the primary user - for example a GitHub user with vigilante mode on have Cursor’s cloud agent sign those commits also so subsequent merges do not become unverified or partially verified?
@Colin Can we please have the option?
I added a rule that explicitly asks not to add the Co-author line to commits. It’s worked for me 90% of the time, it might be useful for y’all while Cursor fixes this.
Edit: wait, i just realized this happens on Cloud Agents regardless of the setting or rules… that’s ugly