Autonomous Commit Attribution

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When using Cursor Agent from the browser, it decides to add its own custom co-author without any user input.

Evidently, there’s a setting for this in the desktop app… I downloaded the app and turned that off (commit attribution), and the behavior persists. It appears the settings don’t actually change anything.

Steps to Reproduce

When using Cursor Agent from the browser, it decides to add its own custom co-author without any user input.

Evidently, there’s a setting for this in the desktop app? I downloaded the app and turn that off, and the behavior process is in the browser.

Expected Behavior

Agents shouldn’t make autonomous decisions about commit patterns without checking with the user.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.1.14
VSCode Version: 1.105.1
Commit: d8673fb56ba50fda33ad78382000b519bb8acb70
Date: 2026-04-14T01:39:23.679Z (1 day ago)
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

gpt-4.5, composer 2

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

This isn’t a bug. Cloud agents add Co-authored-by: Cursor by design, and there isn’t a separate setting to turn it off yet.

The setting Cursor Settings > Agents > Attribution that you found in the desktop app only controls the Made-with: Cursor trailer for commits made via the IDE and CLI agents. Cloud agents browser-based run through separate server-side code and aren’t connected to that setting, so these are two independent mechanisms.

There’s already a feature request for this here: Allow Disabling Cursor as Co-Author In Cloud Agents

If you want this added, it’s best to leave a +1 and your use case there to increase visibility for the team. For now, there’s no way to disable the co-author for cloud agents.

Ah, I didn’t realize these were distinct, thanks for clarifying!