Skip to content

feat(setup): turn off Claude Code attribution through the settings key - #38

Merged
gborges0727 merged 1 commit into
mainfrom
feat/attribution-setting
Sep 9, 2026
Merged

gborges0727 merged 1 commit into
mainfrom
feat/attribution-setting

Conversation

@gborges0727

Copy link
Copy Markdown
Owner

feat(setup): turn off Claude Code attribution through the settings key

Claude Code reads an 'attribution' key from settings.json when it builds
the prompt. Unset, the prompt tells the model to add a Co-Authored-By
trailer to every commit, a 'Generated with Claude Code' line to every PR
body, and a claude.ai session link to both in cloud sessions. The
plugin's two hooks only catch the GitHub MCP tools, so a commit or a 'gh
pr create' run through Bash carried the trailer anyway.

setup.sh takes a new --attribution on|off flag, off by default. Off
writes the key with empty commit and PR text and the session link turned
off, so the instruction never reaches the model. On deletes the key so
Claude Code's default comes back. Other keys in settings.json stay as
they were. The /setup command asks for it as a fourth question.

The cloud bootstrap writes the same key into the VM's user settings,
inline so it does not depend on the plugin's cache path.

Bumps the plugin to 1.28.0 and the rev to 33.

Claude Code reads an 'attribution' key from settings.json when it builds
the prompt. Unset, the prompt tells the model to add a Co-Authored-By
trailer to every commit, a 'Generated with Claude Code' line to every PR
body, and a claude.ai session link to both in cloud sessions. The
plugin's two hooks only catch the GitHub MCP tools, so a commit or a 'gh
pr create' run through Bash carried the trailer anyway.

setup.sh takes a new --attribution on|off flag, off by default. Off
writes the key with empty commit and PR text and the session link turned
off, so the instruction never reaches the model. On deletes the key so
Claude Code's default comes back. Other keys in settings.json stay as
they were. The /setup command asks for it as a fourth question.

The cloud bootstrap writes the same key into the VM's user settings,
inline so it does not depend on the plugin's cache path.

Bumps the plugin to 1.28.0 and the rev to 33.
@gborges0727
gborges0727 merged commit a4fecf7 into main Sep 9, 2026
2 checks passed
@gborges0727
gborges0727 deleted the feat/attribution-setting branch September 9, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant