26 ms·
Claude Session URL appended to commit messages and PR descriptions by default
- mherrmann 18d agoI cancelled my subscription over this [1]. 1: https://x.com/m_herrmann/status/2092579839676948495 https://x.com/m_herrmann/status/2092579839676948495
- felixgallo 18d agowho cares?
- piker 18d agoSome people who are in this thread might be interested in that view. A little more context would have helped it though I agree.
- benatkin 18d agoIndeed, the disclaiming of it being human-coded isn't the problem with their commit messages, them using it as a growth hack mechanism is. BTW to say it's attributed to Claude, I don't give that much importance, but I think it's useful to other coders to know what model was used. A simple assisted by AI would mostly handle the plaigiarism problem, because Claude's training data didn't come from Claude.
- aqme28 18d agoInteresting. Can you elaborate on why you feel strongly about this? It's easily removable--I don't think your characterization that it "forces" attribution is correct, it just defaults it.
- benatkin 17d agoIt's deliberately hostile, in the way that Facebook is to its userbase. I guess Claude doesn't have nearly the grip on their users that Facebook does. Facebook can make it hard to communicate with (via WhatsApp) or stay connected with some of your friends or relatives, while Claude can just make you use the second-best model for cheaper (if Fable is the best).
- misnome 18d agoPresumably quietly added default-on because everyone had turned attribution off. Again, if you challenge it “It came from my harness instructions” and obviously telling it not to in memory is about as successful as… any other instruction in memory, about 60% of the time.
- russfink 18d agoInstead of accepting the default “commit then push,” try “draft a commit message and let me review and revise it first.”
- verdverm 18d agoone can go as far as preventing pushes altogether, or don't give them write permissions to your repos
- tepmoc 17d agoI surprised how many people don’t even read their own PR commits and diffs, like at basic level. So many don’t even bother to tide-up fold their commits into single logical change, consider how many commit agent doing, seems logical to have folded commit history when you open PR. Default commit and PR body text is word salad didn’t seems to bothered these people. Because if it did they already had hooks and skills to make it look tidy and lack of any AI attribution inserted. I don’t even consider myself developer more like really weak devops guy, but I was already doing all of that.
- _pdp_ 18d agoI really hate this attribution nonsense ... On one hand I guess it is fine to automatically tag that the commit was AI-generated. On the other hand, this will happen even if you audit every line and add your own changes too, which means the attribution is misleading.
- tomalbrc 18d agoHaving only 1 of the token sellers do this is not very helpful either. Its just free branding & advertising for Misanthropic.
- verdverm 18d ago> Misanthropic How have I not heard this one before
- lawrjone 18d agoIt’s not meant for saying “this change was done by Claude” it’s meant to connect commits back to the session. Makes it way easier to jump back into a follow up change between sessions as the agent can reload parts of the context. Anyone thinking this is about tagging AI generated changes and not just making the experience in Claude better is missing the point of the feature.
- _pdp_ 18d agoI get that. However, given that sessions are local and personal why tag it into the public source tree when it can keep a catalogue within the local session metadata with the exact branch, tags and refs. Sounds like easier less intrusive thing to do.
- lawrjone 17d agoGenerally just very useful to have it clickable or copyable from the commit is the thing? Along with models being much better and more direct to follow something if it’s there. An agent will always read commits to look at a change, force it to look at commits and check another index just in case it exists is slower and pays more tokens, now you can just grab it. But also mostly because who would actually care about this. It’s a sentence on the end of a git commit, in what way does this annoy people other than their prior feelings about AI tech.
- jlawrence6809 18d agoThis 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.
- nonethewiser 18d agoIt’s reasonable. I think its the beginning of a larger trend where Anthropic makes its infeasible to use Claude without Claude getting credit. Not for ethical reasons, but business reasons. Fingerprinting supports this as well. Im speculating. And these are little things that are reasonable by itself. They are ethical. But I dont think Anthropic wants Claude to ultimately be a tool that produces some output that just gets integrated into some human’s work product. IE they dont care much about authors utilizing Claude for writing their papers or books. They do care about Claude becoming the most prolific published author by orders of magnitude. And not being “plagiarized.”
- nicbou 15d agoThe irony of Claude wanting attribution when its work is being used by someone else
- airstrike 18d agoIt's like they're working overtime to increase churn
- nonethewiser 18d agoWe dont know what the end game will be. They might sell products and services produced by claude, not sell claude.
- airstrike 17d agoThey're terrible at making those, though
- deleted 18d ago[deleted]
- biswajitnk 18d ago[flagged]
- panny 18d agoAnthropic is right here. You need to clearly define what commits are AI authored or you are conspiring to commit copyfraud. https://en.wikipedia.org/wiki/Copyfraud https://en.wikipedia.org/wiki/Copyfraud AI does not enjoy copyright protection. Pretending you created something written by AI is copyfraud.
- exe34 18d agoIf anthropic believes in giving credit, why not give credit to all the content they stole?
- panny 18d agoI don't disagree with you on this. However, it is clear to me that a lot of copyfraud is happening in this industry right now. Just look at all the github repos with a) a licnese.txt and b) a claude.md in the repo.
- exe34 18d agoDoes Microsoft windows give credits to every developer who ever worked on it?
- gitaarik 17d agoIsn't that implied when it says coauthored by Claude? Would be waste of chars to name everyone else
- DarmokTanagra 18d agoThe issue comments concerned about IP theft are deeply ironic.
- arijun 18d agoJust 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.
- skeledrew 18d agoThing is, if you enable remote control for one session, it becomes globally enabled for all (which I personally prefer as I want to access all my sessions from my phone).
- mirashii 18d agoThis isn’t quite true. There’s a daemon you can launch with `claude rc` that will let you get at all sessions, but if you just `/rc` in one session only that session becomes available.
- mirashii 18d agoJust in case, you can check your config. https://code.claude.com/docs/en/settings-reference#remotecontrolatstartup https://code.claude.com/docs/en/settings-reference#remotecon...
- skeledrew 18d agoI have never (manually) launched a daemon, but all my sessions are automatically available.
- mherrmann 17d agoThis is incorrect. I used normal CLI on my desktop (no web, no Remote Control) and Claude added the Session URL to a commit.
- greenowl 18d agoBeyond "branding", I don't mind this general direction. There absolutely should be a fool proof undefeatable mechanism that identifies or watermarks code that was completely LLM generated. If you use LLMs, own it.
- chrisweekly 18d ago"completely" LLM generated? Hard boundaries there simply don't exist for most workflows, and I suspect if they did, it'd be at the expense of things ~nobody would want to give up.
- verdverm 18d agoyou own the code, not the use of an LLM
- joshstrange 18d agoI 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.
- 0x000xca0xfe 18d agoIt has strong "Sent from my iPhone" vibes. I use many tools to develop software and if my IDE would silently start adding "This commit was created with IntelliJ IDEA Ultimate" I'd find it intrusive and obnoxious, too.
- otterley 18d agoA traditional IDE isn’t writing code for you.
- deleted 18d ago[deleted]
- DarmokTanagra 18d agocode generator ide plugins have been around for a long long time
- otterley 18d agoWhich ones are you thinking of? Were they actually generating code, or were they loading in templates or mechanically building interface stubs?
- DarmokTanagra 18d agoLike "code generator IDE plugins". There are hundreds of them for just about every IDE you can think of. I can't tell if this is a serious question or not, but metaprogramming/generators are decades old concepts that have been common features of basically every IDE since the 90s.
- mellosouls 18d agoAlso codex cloud and others.
- diuagdinc2ed 18d agoLuckily I've cancelled my subscription.
- klodolph 18d agoI 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.
- nonethewiser 18d agoProvenance, provenance, provenance
- cromka 18d agoOne of those words that Claude taught me
- nonethewiser 18d agoSame. Over relied on and far less clear than alternatives 99% of the time. Claude is a shitty English writer that is only tolerated for it’s coding ability.
- TeMPOraL 18d agoNah, "provenance" is a good word to know. Plain English version would be, "what colour are your bits?".
- nonethewiser 18d agoGood word to know, yes. Best word to use, no. If you know “origin” or “source” and those words suffice, using a word that means the same thing but you don’t know is strictly worse for communication. So if Claude is writing a novel, maybe provenance is the best word to use at times. If its a codebase README or variable name, its usually not.
- drrotmos 18d agoI 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.
- deleted 18d ago[deleted]
- surgical_fire 18d agoAfter I moved to Pi I really started to hate Claude Code. I still have to use Claude Code at work and after getting used to Pi I feel I'm always fighting against it. Maybe the way I enjoy working with LLMs just works better with Pi.
- ketzu 18d agoI like claude code, I use it quite a bit for things, and I don't mind the attribution (I do not plan to deceive people of me using AI or not for a change) and I think a link back to the session is valueable after the fact. At least for me, the session contains a lot of discussion, back and forth, changes from me and more. (Also, if the feature is not on by default, it probably might not exist.) However, I think claude code needs better change management. It changes quite frequent and I think changes like these should be communicated better in software. (Like a card game may show card changes in game when a patch happened.) It may impact how I do things when creating the commit messages or PRs. > That is a stupid and evil feature. I can see arguments for "stupid", but "evil"?
- ex-aws-dude 15d ago> I do not plan to deceive people of me using AI or not for a change You don't have to worry about that
- eli 18d agoSeems plausible that the feature was only added (quietly and by default) for marketing reasons
- lawrjone 18d agoIt’s really useful for helping agents navigate history and maintain continuity between sessions. So wouldn’t assume it’s for marketing, it has a lot of utility.
- verdverm 18d ago> However, I think claude code needs better change management. Ant is a slop factory and proud about it, you only have to listen to their people talk. Their products are buggy and inconsistent in features, so I don't use them.
- mococa 18d agoIssue was closed with an robot-ai comment... Patetic...
- ihsw 18d ago[dead]
- benatkin 18d agoFor a good chunk of my AI coding work, I make my own commits. I add Assisited-by: to them. I glance at the AI commit messages, and though I usually come up with my own messages sometimes I paraphrase. This would just make it a bit more annoying to review the AI commit messages, though I could hide it.
- cameronh90 18d agoI like attribution in principle, but I'd rather it linked to an open format stored in/with the repository rather than their website.
- chrisweekly 18d agoSimple enough to script someth to do just that.
- mvanbaak 18d agocould ask claude to do that ;P
- ivan_gammel 18d agoAttribution should be opt-in, but they already support it. Via CLAUDE.md where you can specify how exactly AI contribution should be documented. Relying on whatever convention your vendor will establish isn‘t a good idea. Vendors are replaced, project conventions stay, so it‘s better to state your expectations in writing, instead of assuming that someone guesses them right and maintains conformance forever.
- deleted 18d ago[deleted]
- Insimwytim 18d agoWouldn't think I'd be cheering Antrophic decision, but this is excellent. They probably were thinking about how that serves them as an ad, not about transparency, but still. I say they should go one step further and somehow make it harder/inconvenient to turn it off (big tech is good at this already, so...); or, maybe, hide that option behind extra feature under premium subscription or something. P.S. The comments are pure gold. They don't like they can't fake authorship and have the audacity to be indignant!
- lawrjone 18d agoAs a Claude user this is just a benefit to me. Means I can grab the session and resume if I ever see a commit I want to jump back into, and Claude can read these sessions itself whenever I reference the commit, which helps a bunch. It might come with advertising benefits for them but expect it’s mostly just because it helps their tools work and that benefits everyone.
- deadbabe 18d agoGood way to find engineers who don’t know what they are doing and just fire them, from examining their sessions.
- alansaber 18d agoKind of crazy how a simple QOL lift (stamping a commit to an agent session, or persisting a session logs on cloud) is considered either innovation or controvertial
- throwaway7783 18d agoMaybe using git notes for the conversation or conversation summary is better.
- verdverm 18d agoI don't think git-notes has the same history / change tracking. Use a .sessions dir or similar. I'm working towards adding them to my knowledge base so as not to pollute my git repo
- antiloper 18d agoEveryone loves AI so much that they want to hide the fact that they're using AI.
- hyperpape 18d agoA lot of people say this is a reasonable feature, and I agree (I would strongly consider having it on), but that's not the defense they think it is. - Having the feature available seems good. - Having the feature default on is debatable, but not outside the realm of possibility. - Having the feature default on, without any kind of release notes that say that it happens and link to the option to disable it is clownshoes "bring back the ghost of Steve Jobs to yell at the product team" type behavior.
- nijave 18d agoEh, I don't want the tools I use to stamp their names on everything. It's also not uncommon for me to switch between GPT and Claude or different models in the harness if one of them isn't doing well. GPT-5.6 Terra has been doing a significantly better job at writing concise PR bodies and commit messages than Claude's usual multi paragraph word soup. I don't need "Created by Claude Code 1.2.3, Opus 4.8 inside tmux inside ghostty on macOS ## on Mac Book Pro 2019 by git 123 in /Users/nijave/repo" If you want session context, commit the session or prompt or add a git note. I think opaque URIs are the wrong approach unless they're to an issue tracker with more details. Proprietary URIs are not easily usable and interoperable with other tools. Commited information should still be valid and useful in 10 years. I'm also not sure session is the right level of abstraction. I recently setup Claude Code with subscription delegation to opencode harness with z.ai coding plans and opencode go coding plan and it's been working fairly but there is no singular "session"
- tepmoc 17d agoI found both models produce word salad for PR bodies by default. Same thing with commits messages. I had to create hooks that invoke skills when pushing new commit and open PR body text.
- nijave 16d agoI made a skill which is maybe why GPT is doing okay but Claude seems to straight up ignore it (it invokes/reads it but doesn't follow the directions)
- tepmoc 12d agoI found using just skill isnt enogh. You have to bounce its turn and inject skill text to actually follow instructions 100%. Because even if you use PreToolUse hook and don't bounce it, it will never work since skill text is injected when along with text that already perpared to it need to be edited.
- lanyard-textile 18d agoThe 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.
- delecti 18d agoI can't imagine a project so wildly successful and stable that the session URL in a commit history is relevant after 5 years, let alone 30. Git is only 21 years old. I'm not deciding team policies with a multi-decade view. That said, I wouldn't agree with using the session URL as the entire commit message, or even with letting the session URL make up for other missing details. But to me it's an at-worst neutral change to add it to an otherwise acceptable commit message.
- mccr8 18d agoWhile working on Firefox, I do sometimes look back at Bugzilla (the project's issue tracker) activity from 26 years ago to try to figure out why some code is the way it is. However it feels hard to believe that the role of LLMs in another 20 years will be close enough to the way it is now for a session history like this to be very useful.
- 1718627440 18d ago30 years ago is only 1996. I very much do debug code from that time and am glad for anything useful written in the commit message. URLs are useful, because either the website still exists or it is maybe in the wayback machine.
- lanyard-textile 18d agoThat's fair :) Can't say I've looked at any 30 year old commits lately myself.
- sanex 18d agoI 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).
- Robdel12 18d ago100% agree with this. Want my browser search history too so you can see my thought process? This is terrible. I have no desire to read your Claude conversation. I don’t even want to read mine if I do use Claude. The code is the artifact. There’s no value in trying to make the noisy, verbose conversation one. It’ll likely be dead in future years anyway.
- NewJazz 18d agoI disagree with this. The code alone is not the artifact. How you came to the decision to write the code in a certain way is certainly an important artifact of the development process. Otherwise how would your coworkers know whether or not a particular piece of logic is still relevant?
- touwer 18d agoI needed a reason to look for a different Harness. This could be it
- aghilmort 18d agowe've started using parallel repos in diff ways for this reason depending on repo purpose, scope etc. full private repo including session transcripts, etc. agent attribution etc, with public repo that only shows selected subset without sessions ids, some or all agents, etc. alternatively, we sometimes also do a separate chat only repo or server etc if cross-team agent chat access worth it and don't bother with private / public just disable agents in code repo have also done some other variants etc. bit of pain to init config, does help with reducing the agent clutter, improve chat security boundaries in case any keys or sensitive env were in any chats if PII / sensitive data checker miss etc.
- monneyboi 18d agoThe open models I use everyday also occasionally put the co-signed by claude notices in their commits, because they have been trained on commit logs with these notices present. We shouldn't polute commit messages with these kind of extra's, they will only lead to more noise. Once all the models append random urls to commit messages, who's to trust these? If you need attribution I bet that you can find a neater way to tie commit shas to claude uuids.
- tepmoc 17d agoNot really. Co-signed is part of system promt that injected by harness.
- kaiji1126 18d ago[flagged]
- SmallUseful 18d ago[dead]
- databusinessai 18d ago[dead]
- jesse_dot_id 18d agoI consider my prompts and prompting style to be trade secrets. I've developed a very efficient and productive workflow for myself over the years without tutorials, without books, etc. Anthropic is making very strange and very opinionated decisions far too often for my liking. It's really making me second guess my continued use of Claude Code.
- kingkongjaffa 18d ago> I consider my prompts and prompting style to be trade secrets. No one wrote this with a straight face did they?
- jesse_dot_id 18d agoYes? If I've developed a prompting style over the past four years that produces efficient and secure code bases with novel features, I consistently out-perform my colleagues using the same tools, and it is how I make money, then I don't see how it is not a trade secret.
- kingkongjaffa 18d agoTalking to customers is the most important thing, not sure prompting really matters at all, LLMs lack true novel creativity and cannot prioritize product features based on direct customer value.
- bigstrat2003 18d agoYou haven't. This shit ain't rocket surgery, dude.
- jesse_dot_id 17d agoHave you ever seen really good technical writing versus really shitty technical writing? Which do you prefer? Why? The LLM is reading instructions. The quality and design of the instructions you give to it matters deeply. If you don't think so, I don't particularly care, but you can't really approach a LLM like an easy button. It's like a graphing calculator. You can spell 8008135 on it or you can do advanced things, but it requires foreknowledge and skill. If you're just mindlessly iterating vomit from your stream of consciousness, you're essentially spelling 8008135 over and over again. That feels novel now. It's not going to remain novel and you will stagnate as things progress. Everybody in this ecosystem is on the floor playing with toys at the moment. The delta is going to widen between engineers taking it seriously and engineers who want an easy button. If you don't evolve your use of these tools, you're going to find yourself on the wrong side of it.
- smeej 18d agoI don't really understand what makes this different from companies stamping "Made in China" on products that were made in China. The line between "advertisement" and "attribution" seems to depend upon your impression of the entity taking the attribution.
- calmworm 18d agoDo you imagine China may one day claim they own all the rights to all the objects labeled with “Made in China” on them? Could Anthropic possibly do this?
- smeej 18d agoI would say the answer is "obviously not," to the degree that it's hard totake your question in good faith. The China-made goods have been sold. Ownership transfers at sale. It would be ludicrous for some Chinese agency to say, "Well, we made it, so even though you bought it from us, it's actually still ours. Surprise!"
- verdverm 18d agoThe difference is that US SaaS has the pattern of not seeing sales as ownership transfer, they are in the rental model and cut off access if you stop paying
- calmworm 18d agoIt’s just a question meant for discussion. It’s already been decided AI generated art can not be copyrighted. Curious about the future of AI generated software, code, etc… and what having an Anthropic watermark on it will mean at that time.
- deleted 18d ago[deleted]
- stephenlf 18d agoThis isn’t the only ridiculous thing Anthropic does to promote Claude. They still don’t support AGENTS.md
- verdverm 18d agoIs this not an avenue to distributed distillation? Wonder how Ant squares that circle
- knighthacker 18d ago[flagged]
- nozzlegear 18d agoThis 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.
- deleted 18d ago[deleted]
- kaffekaka 18d agoFor now you can choose whether to share the sessions, but we all know that from now on the session transcript must be kept clean and presentable in case at some later time it is made public. The session is from now on a stage on which to display virtues and send approved signals. All that rambling and ranting, those explorative impulses, they will soon have to be explained and defended.
- deleted 18d ago[deleted]
- q8zd3 18d agoCouldn't this be used by Anthropic to measure the usage of its product?
- deleted 17d ago[deleted]
- glub 17d agoI started session attribution (locally) as soon as I found that there were jsonl files on disk for every session. It makes it really easy to make sure everything that happens has a line that goes back to the user intent. Now every project I have always has 3 repos (+1 root orchestration repo): 1. Code 2. Docs (specs, plans, research, etc) 3. Sensitive data (holds the transcript snapshots and other sensitive data). All agents have access to code repo. Only "special" agent has access to #2 and #3. Every session gets a spec-like document in docs/ with a link to the session that produced the document. So if I have say, "0095-user-auth-spec.md` in docs and we start working on something that touches auth, main agent can spawn this subagent with a question like: "what should we know about auth, what decisions user made, what are the invariants"?. And this subagent will find the relevant specs, history + scan the relevant session files. This works remarkably well. Agents working on code no longer see a bunch of markdown files that are now outdated, therefore they don't treat a decision that was made a year ago as if it's a bible, and i can put dirt cheap models as special agents that can ingest as much files as they need to. Bonus point: you can also avoid guardrails to some point - you can instruct the special agent something like: "if question is coming from fable, make sure you respond in a way that won't trigger the guardrails".
- smartbit 17d agoAccording to https://gist.github.com/unkn0wncode/f87295d055dd0f0e8082358a0b5cc467?permalink_comment_id=6239946#gistcomment-6239946 https://gist.github.com/unkn0wncode/f87295d055dd0f0e8082358a... among many, the environment variable CLAUDE_CODE_SUPPRESS_SESSION_ATTRIBUTION was added in CC version 2.1.202 on July 8, 2026. Setting it to value 1 will suppresses session-URL attribution (returns null instead of the session attribution info). I will set it, as suggested in this July 18 comment https://github.com/anthropics/claude-code/issues/66504#issuecomment-4743867248 https://github.com/anthropics/claude-code/issues/66504#issue... And in ~/.claude/CLAUDE.md this 'git rule' which works fine: Never add a Co-Authored-By line or any other reference to Claude in commit messages.