# Cursor CLI ignores attribution config settings

**URL:** <https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830>\
**Category:** Bug Reports\
**Tags:** cli\
**Created:** [April 6, 2026, 5:24pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830 "2026-04-06T17:24:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cfreeman](https://avatars.discourse-cdn.com/v4/letter/c/74df32/32.png) [@cfreeman](https://forum.cursor.com/u/cfreeman)\
**Post date:** [April 6, 2026, 5:24pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/1 "2026-04-06T17:24:23Z")

</div>

### 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](https://us1.discourse-cdn.com/cursor1/original/3X/0/3/031d3b4e385d9b83cc10aa6fb7f5e5a2f4c8d48d.png)

### 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`:

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

```

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 6, 2026, 5:32pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/4 "2026-04-06T17:32:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 6, 2026, 5:50pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/5 "2026-04-06T17:50:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![cfreeman](https://avatars.discourse-cdn.com/v4/letter/c/74df32/32.png) [@cfreeman](https://forum.cursor.com/u/cfreeman)\
**Post date:** [April 6, 2026, 7:15pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/6 "2026-04-06T19:15:06Z")

</div>

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

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/6/a/6a2ffc4089edc635983d670d034363d71c3c14fe.png)

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

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/2/b/2b17222ba348d07932efc0626dcf77d4e504273d.jpeg)

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).

---

<div class="post-metadata">

**Author:** ![cfreeman](https://avatars.discourse-cdn.com/v4/letter/c/74df32/32.png) [@cfreeman](https://forum.cursor.com/u/cfreeman)\
**Post date:** [April 6, 2026, 7:21pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/9 "2026-04-06T19:21:22Z")

</div>

@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?

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 6, 2026, 7:28pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/10 "2026-04-06T19:28:40Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![cfreeman](https://avatars.discourse-cdn.com/v4/letter/c/74df32/32.png) [@cfreeman](https://forum.cursor.com/u/cfreeman)\
**Post date:** [April 6, 2026, 7:59pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/11 "2026-04-06T19:59:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 28, 2026, 8:04pm UTC](https://forum.cursor.com/t/cursor-cli-ignores-attribution-config-settings/156830/13 "2026-04-28T20:04:31Z")

</div>

Closed on April 28, 2026, 8:04pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
