attribution setting does not control session URL in commit messages
Problem
The attribution setting in ~/.claude/settings.json allows removing the "Co-authored-by" trailer and "Generated with Claude Code" text from commit messages:
{
"attribution": {
"commit": "",
"pr": ""
}
}
However, this does not remove the session deep link URL (e.g. https://claude.ai/code/session_01SBzqph11q7ZSHA5QEGgtu5) that Claude Code appends to commit messages and PR descriptions.
There is no documented setting to control this behavior.
<img width="1102" height="506" alt="Image" src="https://github.com/user-attachments/assets/e4a9ec8e-a830-4c6d-a7c5-7604db925f2e" />
Why this matters
- Users who set
attribution.committo""clearly intend to have clean commit messages with no Claude Code metadata. The session URL should respect this intent. - The session URL leaks information about the tooling and specific session used to produce the code.
- For users running Claude Code in the cloud (e.g. via
claude.ai/code), a localcommit-msggit hook is not a viable workaround since the commit is created server-side.
Expected behavior
When attribution.commit is set to "", all Claude Code metadata should be removed from commit messages, including the session URL. Alternatively, provide a separate setting to control the session URL independently.
Reproduction
- Set
~/.claude/settings.jsonto:
``json``
{
"attribution": {
"commit": "",
"pr": ""
}
}
- Use Claude Code (cloud) to make a commit.
- Observe that the session URL is still appended to the commit message.
6 Comments
https://t.me/+t_ed3b95DqczNmU1
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This is still relevant. I don't think it is worth opening a new issue
This is now configurable with the
sessionUrlkey underattribution. Was added in v2.1.182. Docs: https://code.claude.com/docs/en/settings#attribution-settingsThat works for your local configuration, but there is no way to control this for claude on the cloud.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.