I’m getting pretty frustrated with how Cursor handles Git attribution with Cloud Agents.
Initially, disabling the attribution settings didn’t seem to do anything. Cursor was still creating commits with Cursor as the author and me only listed as the co-author.
Then at some point, without me changing anything, Cursor started creating commits where even my co-author attribution was gone entirely.
I’ve worked around it now by adding a global Cursor rule that explicitly forces commits to use my configured Git name/email, but I don’t think this should be necessary. Having an agent unexpectedly change commit authorship means I have to rewrite Git history afterward, which is really not great.
Steps to Reproduce
Disable Git Attributions, do some work with a Cloud Agent, git attribution is still authored by Cursor with myself as the co-author.
It works fine when not using Cloud Agents by the way.
Expected Behavior
I honestly don’t expect Cursor to be the main author at all, even with attribution enabled - especially with tools tracking contributions that don’t cover co-authors it creates a few issues.
Quick explanation of what you are seeing. The Attribution toggles in the dashboard only control the extra “Co-authored-by: Cursor” trailer and the “Made with Cursor” PR footer that the IDE and CLI agents add to commits you author yourself. That is why turning them off works locally but changes nothing for Cloud Agents.
Cloud Agents work the other way around. Commits made on a hosted Cloud Agent are always authored as Cursor Agent, and you (the person who started the run) are added as a Co-authored-by trailer. There is currently no setting to make you the primary author. There is an existing feature request for exactly this, and adding your voice there is the best way to push it forward: Allow Disabling Cursor as Co-Author In Cloud Agents
Your rule that sets your git name and email is a reasonable workaround for now. One caveat: those commits will no longer show the “Verified” badge on GitHub, since the signing key belongs to the Cursor Agent identity, and GitHub only links them to your profile if the email you set is verified on your GitHub account.
On the commits where your co-author line disappeared entirely: the trailer is added by a commit hook on the agent machine, so it gets skipped if the agent commits with --no-verify, if the message already contained a Co-authored-by line, or if a tool in the repo (for example husky or lefthook) reinstalls its own git hooks during the run. If you still have that agent run, could you check its transcript for the git commit command it used and share what you find? That would tell us which of those it was.
just fyi, I removed the Git rule because it wasn’t consistent.
