Allow disabling "Made-with: Cursor" commit trailer

Ideas Feature Requests
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I use Cursor’s agent for commits, and it adds a Made-with: Cursor trailer to every commit message. I don’t want this for several reasons:

Clean history – I prefer plain, professional commit messages without tool attribution.
Team rules – Some teams forbid AI tool mentions in commits and PRs.
No choice – There doesn’t seem to be a way to turn this off; the trailer is added even when I don’t use --trailer.
Extra work – To remove it I have to rebase/amend outside Cursor, which is tedious and error-prone.

Request: Add a setting (e.g. in Cursor Settings → Features or Git) to disable injecting “Made-with: Cursor” and similar trailers into commit messages, so users can opt out when they don’t want attribution in their history.

Steps to Reproduce

Just using custom command in cursor:

commit-local-changes

Things to keep in mind:

  • No mention of Cursor in commits: Do not add “Co-authored-by”, “Done by AI”, or any Cursor/similar phrases to commit messages. When creating commits from the agent, use only the subject/body you write (e.g. git commit -m "message" or -F file). If the environment still appends Co-authored-by, tell the user to amend or rebase in a terminal outside Cursor (where that injection does not run) to remove it.
  • No use of --trailer in the commit, it is strictly prohibited
  • If added by mistake, then use amend to remove it yourself, don’t ask user to do it.

Could you check our local changes using git status, and create 1 or multiple commits with appropriate messages?

Screenshots / Screen Recordings

स्क्रीनशॉट 2026-03-11 235633
स्क्रीनशॉट 2026-03-11 235633528×432 16.7 KB

स्क्रीनशॉट 2026-03-11 235739.png
स्क्रीनशॉट 2026-03-11 235739.png524×411 12.3 KB

Operating System

Windows 10/11

Version Information

Version: 2.6.13 (user setup)
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

This is already a setting. Cursor Settings → Agents → Attribution → Commit Attribution & PR Attribution

5

Wow.

Thanks buddy @user927

6

It stoped working, I have both disabled but it still adds those, same applies for cli agent as well.

7

The issue has another layer:

When Cursor shows the “git commit” command in its “Shell” tool, a “–trailer” parameter is visible. However, even when the parameter is manually removed before running the command, Cursor still adds the trailer.

This in itself is unacceptable.

Cursor must never autonomously modify a command once the user has verified or edited the exact command string. Cursor must execute user-reviewed commands verbatim as they are presented beforehand, without any post-edit mutation.

8

Can we disable the addition of the trailer to git commits on Cursor CLI?

9

I modified the .cursor/cli-config.json manually and it worked. Modify these 2 settings to false:

"attribution": {
"attributeCommitsToAgent": false,
"attributePRsToAgent": false
}

If we ask the AI model to do it, the CLI will revert the changes, so we must edit the file manually.

11

yes I agree with you. It looks like there are extra agent that run beyond the one I am directly talking. Because I could remember telling cursor to remove it, it tried like over 6 times before it give up and said something is adding it, so cursor had to give me the script to run manually to automate the commit edit. This begs the question on how our cursor works, and if you could include feature like that, what if the agent do something behind my back that I didn’t know, maybe of the allowed codebase or something. We need to have an audit log or something, that show all what is going.