What's this about?
Claude Code began appending the Claude session URL to commit messages and PR descriptions by default. The GitHub issue is long and the reception is hostile. The complaint is not primarily about attribution — it is that a default-on link is being written into permanent, public, shared project history, and that turning it off in memory or instructions works about as reliably as any other memory instruction.
What is the actual privacy question here?
A session URL is a pointer into a conversation. Even if the link requires authentication to open, its presence in a commit message is a permanent public record that this change came from an AI session, which session, and roughly when — in a repository whose history is cloned by everyone who touches the project and is effectively impossible to rewrite once pushed. The reasonable objection is not "I am embarrassed"; it is that a tool wrote identifying metadata into an immutable shared artifact without being asked.
What's the community saying?
- The prevailing theory for why it is default-on: attribution had been widely turned off, and this is a way of getting it back.
- The accuracy objection: the attribution is misleading when you have audited every line and added your own changes, but the commit still says the session produced it.
- The framing that gets the most agreement is that the problem is not disclosure but distribution — using developers' commit history as a growth channel.
- A milder counter-position: knowing which model produced a change is genuinely useful information for other coders, and a simple "assisted by AI" would cover the honesty requirement without the link.
- At least one user publicly cancelled a subscription over it, and several point out that a single vendor doing this amounts to free advertising in everyone else's repositories.