Commit attribution opt-out ignored

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have commit and PR attribution turned off, but Cursor continues to sign commits as cursoragent. Have tried restarting Cursor and starting a new session.

Steps to Reproduce

Turn off commit and PR attribution, then have Cursor push a commit.

Expected Behavior

Commits are attributed to the user instead of cursoragent

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.8.23
VS Code Extension API: 1.105.1
Commit: 7cf19b7482706625cdb70db3211b7dd035b7aa30
Date: 2026-06-23T14:57:42.334Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This isn’t a bug, it’s how two different attribution systems work.

The toggle Settings > Agents > Attribution that you turned off only removes the Made with Cursor trailer from commits and PRs made by the local IDE or CLI agent.

The signature Cursor Agent <[email protected]> is added by cloud or background agents. They run on our side server-side and always commit under that identity, then add you as Co-authored-by:. The IDE setting doesn’t affect them, it’s a separate path. There isn’t a separate toggle for cloud agent authorship yet. This is a known gap and I can’t share an ETA.

Workarounds for now:

  • A local or CI hook prepare-commit-msg or commit-msg that strips lines containing [email protected]
  • Squash or amend on merge to change the author

If your commits are actually coming from the local IDE agent and not cloud or background, share the Request ID and describe the flow in more detail and we’ll take a closer look.

Related threads: