Cursor adds commit attribution despite disabled user preferences #26889

What happened

Cursor adds a Co-authored-by: Cursor trailer to commits made through T3 Code, despite these settings already being present in ~/.cursor/cli-config.json on the server machine:

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

Diagnosis

The problem originates in Cursor’s local SDK configuration path:

• T3 passes the user settings source.
• The SDK runner forwards those options to Agent.create or Agent.resume.
• The published SDK’s local resource creation does not supply attributionConfigProvider.
• Request-context construction consequently falls back to true for both attribution preferences.

Read-only inspection and runtime tests confirmed this in SDK 1.0.38 and latest 1.2.0. No supported public attribution option was found, so upgrading to 1.2.0 alone does not fix it.

Steps to reproduce

1. Set both attribution preferences to false on the machine running the T3 server.
2. Open a fresh Cursor thread using T3’s local SDK provider.
3. In a disposable repository, request a commit and inspect the incoming shell tool call before execution.

The command can already contain a Cursor Co-authored-by trailer. T3’s outgoing prompt does not request attribution.

Expected: explicit false must disable the corresponding request-context attribution field.

Version and environment

• T3 Code Desktop 0.1.4 on Windows, connected to its WSL/Linux server 0.1.4.
• Installed @cursor/sdk: 1.0.38.
• Protocol: cursor-agent-sdk.local.
• Independent regression tests: WSL/Linux, Node 24.14.0.

Evidence

A credential-free loopback integration test exercised the real SDK through create/resume and captured its actual request context:

Input: both attribution preferences false

Expected:
  commitAttributionMessage absent
  prAttributionMessage absent

Actual:
  commitAttributionMessage = "enabled"
  prAttributionMessage = "enabled"

Missing/empty settings and explicit-true cases passed. All explicit-false cases failed on both tested SDK versions. No model inference, commits, or PR creation were needed.

Related issues

No matching T3 issue was found. Cursor’s GitHub repository has issues disabled.

Fix applied or workaround

None. The installed runtime and user repositories remain unchanged.

The likely upstream repair is to carry the attribution settings provider through local resource creation, preserving independent commit/PR preferences and existing defaults when settings are absent.

Prepared by lab/gpt-6.1-sol through OpenCode in T3 Code.