Cursor CLI ignores attribution config settings

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I’ve disabled commit and PR attribution in both the Cursor app and in ~/.cursor/cli-config.json but the CLI is still adding the --footer flag when committing.

Steps to Reproduce

Have Cursor CLI create a commit in any repo. It will add the attribution footer no matter what config settings you have.

The agent will also think it didn’t add --footer, so it appears that it’s being added programatically.

Expected Behavior

Cursor CLI should respect attribution config

Screenshots / Screen Recordings

image
image756×210 19.5 KB

Operating System

MacOS

Version Information

❯ agent about
About Cursor CLI

CLI Version 2026.03.30-a5d3e17
Model Composer 2
OS darwin (arm64)
Terminal ghostty
Shell zsh

Additional Information

This is what I have in ~/.cursor/cli-config.json:

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

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report. I see the config has attribution turned off, it looks like the CLI really isn’t reading those settings.

I passed it to the team. No timeline yet, but your report helps us prioritize.

If you find a workaround, let me know. It could help other users.

1 Like
5

Also, I can’t reproduce this bug on the latest CLI version. Try updating with agent update and check again, it’s probably already fixed.

6

@deanrie According to agent update I am on the latest version (2026.03.30-a5d3e17).

image
image676×502 49.1 KB

I tried testing this again and got the same results. Here’s the conversation:

image
image1920×2042 374 KB

You can see where it’s getting added programmatically since the tool call itself doesn’t contain the --trailer flag, and the model is convinced it didn’t pass it.

No changes to my config or anything (still have everything disabled).

1 Like
9

@deanrie Ok, have some more info for you.

Everything above is from my work account (which is an Enterprise plan).

Tested the exact same setup on my personal account and can confirm that disabling attribution in the config does indeed work for my personal account.

I wonder if the fact that I’m on an Enterprise plan at work is affecting things here. Any chance Cursor CLI on an Enterprise plan has some kind of managed settings that would cause it to ignore my global config file or something?

10

This is really helpful info that everything works as expected on a personal Pro account.

It looks like the cause is the Enterprise plan. Enterprise has admin-managed settings that can override local user configs, including attribution settings. If your team admin enabled forced attribution in the dashboard, your local cli-config.json will be ignored by design.

I’d recommend checking with your Enterprise admin. In the team dashboard settings, there should be options to manage attribution at the team level. If attribution is forced on there, only an admin can change it.

Let me know if this ends up being the issue.

11

Yep, that’s what did it. We don’t have “Disable attribution” checked in our team settings, so that appears to translate to “enable (and force) attribution”. Not a huge deal, though a bit surprising IMO to have not checking a box translate to “override config files”.

Either way, looks like we got to the bottom of it! Thanks for helping me debug. Feel free to close this.

1 Like