Where does the bug appear (feature/product)?
Cursor SDK
Describe the Bug
Every commit my SDK-driven agents make carries Co-authored-by: Cursor <[email protected]>, and I cannot turn it off. I already set attribution.attributeCommitsToAgent: false in ~/.cursor/cli-config.json. In the installed dist, computeCachedRequestContext gates the trailer on attributionConfigProvider?.get()?.attribution?.attributeCommitsToAgent ?? true, but createLocalExecutor never populates attributionConfigProvider, so the opt-out is unreachable and commitAttributionMessage defaults to "enabled". The agent then appends --trailer itself. No public option exposes this: AgentOptions, LocalAgentOptions, and CreateLocalExecutorOptions declare no attribution field, and settingSources loads hooks, MCP, rules, and skills but never cli-config.json.
Steps to Reproduce
I set ~/.cursor/cli-config.json to {"attribution":{"attributeCommitsToAgent":false,"attributePRsToAgent":false}}, then ran a local agent via Agent.create({ apiKey, model, local: { cwd, settingSources: ["user","project","plugins"], store } }) and asked it to commit. Across 44 commits in my transcripts, the agent issued git add -A && git commit --trailer "Co-authored-by: Cursor <[email protected]>" -m "..." every single time, and all 23 non-merge commits carry the trailer. No git hooks are installed and core.hooksPath is unset locally and globally, so nothing but the agent’s own flag adds it.
Expected Behavior
I expect the local executor to honor attribution.attributeCommitsToAgent from cli-config.json, or for a documented attribution option on AgentOptions / local executor options to let me disable the commit trailer.
Version Information
@cursor/sdk 1.0.24, Node v20.11.0, Linux 6.12.67-linuxkit (Docker), local executor with settingSources [user, project, plugins]