Claude Code appends session URLs to every commit and PR by default — users demand opt-in
Claude Session URL appended to commit messages and PR descriptions by default
A GitHub issue on the anthropics/claude-code repository reports that Claude Code automatically appends a session URL (e.g., https://claude.ai/code/session_...) to commit messages and PR descriptions by default, with no prompt or warning. Users find this unprofessional and a potential privacy leak, especially in public repos. The issue suggests making it opt-in or at least opt-out with a discoverable setting. Maintainers closed the issue, noting a setting exists to disable it, but users argue the default should be off. The discussion highlights broader concerns about default-on attribution features in AI coding tools.
This is some serious BS--that it does this on by default. WTH, Anthropic??
- klodolph
I may be missing something, but this is exactly what I want as a default. I want the session links there. I see PRs from my coworkers with session links.
I still get to control whether other people can see the session, but I don’t lose it.
I don’t get the “unprofessional” argument. This is attribution. Attribution is professional. If you don’t want it, you turn it off or rewrite the commit messages. If you are having Claude write the commit messages FOR YOU and you are NOT READING THEM then that’s what’s unprofessional. I am honestly kind of shocked and disappointed by how upset people are by this.
- nozzlegear
This is a good default for new users, but shouldn't have been turned on for existing users without prompting them first.
I don't use Claude so no dog in the fight.
- sanex
I can't believe how many people are in favor of it. Like it's so positive in the comments I'd think it's astroturfing. The code is the result of my work however it got done, and if I don't document or explain it well enough then that's a separate issue. Did you want to see my slack messages to my mentor too? Or how about all the stack overflows I read? Maybe I should voice record all the times I swore about Gary the junior dev not documenting something?
It's plenty obvious when the code is AI written it's probably just safe to assume 95% of things have been at least AI assisted. Just look at the drop in SO volume, we're not writing less code we're writing more (rip GitHub uptime).
- lanyard-textile
The major problem I see with these are linkrot. Do any of us truly believe these links will work 30 years from now?
Post IPO, many years down the line, a leadership that is eager to cut costs will look at their storage usage and expire 7 year old non-training sessions. Quickest thing to go. I have zero faith in any successful provider getting this right.
Git is supposed to be the durable storage medium, self containing and weathering the passage of time. Now we're littering the repos with a bunch of URLs that are only helpful in the short term.
- joshstrange
I don't see any issue with this at all. I noticed it the other day and thought it was convenient. The same way I let the agent tag the PRs/commits with its name. I want to know what was used, in fact I wish it would identify the model used.
I'm not embarrassed by my LLM usage and I want to provide a full audit trail whenever possible to aid myself in the future.
PS: Claude archives old conversations on your computer after 30days. I've started archiving mine to the side as well for potential future use.
- arijun
Just because it's not in the title and most people won't be scrolling all the way down: its only enabled for web and Remote Control sessions, per a maintainer.
- jlawrence6809
This is probably a controversial take, but I love this. Back in the early days of claude code I had to write a script (well, claude wrote it) to pull out the session id and append it to every commit. It's a lifesaver when you are trying to debug an old commit to pull up the chat session that actually wrote it.
- drrotmos
I really like working using Claude Code, but Anthropic has a really bad tendency to push out new "features" like this as default-on, through auto-update. That, and their models trying to do everything through bash (including editing files) is enough that I'm seriously looking in to switching harness to pi.