Keep in mind that if you run across someone else's spam in the Git logs:
- You need a Claude account.
- You need permission to view the session.
The only people who can just follow that link and look at how Claude was used, is Anthropic themselves. Therefore, they can also use it as an additional mechanism to tie sessions back to other IDs/identities. For everyone else this is "Sent from an iPhone" but longer.
One thing I'm not sure about: what is the utility of linking to the session? What are folks expected to do with that data?
If the tool auto-does it, yes.
What's the odds on them fixing that bug anytime soon.
Having it in the commit message is handy (not to mentioned I already have it I. The commit message).
Models change so much that I don't really see why anybody cares what model was used to generate the code after the fact. It changes every few months and they're non-deterministic so its not like you'll ever "recreate" the same conversation yourself anyways.
One could argue that "https://claude.ai/<uid>" is slightly more verbose over "CLAUDE_UID=<uid>", but the former is also slightly more convenient for those with access to the transcript, and both have word "claude" in them, because you need to be able to tell which UID in the commit message is for what.
I prompted what amounts to verbose “I want X” and then did QA. I’m perfectly happy with an LLM being credited with that code and there being no copyright existing for that code.
For some people that is their life’s work and they want to clutch pearls. Their sole contribution was a half baked idea and they shipped QA out to their “users” but they want to be credited with any rights.
There is definitely a continuum in LLM usage for code, do I agree with an AI blindly stamping every commit, not really.
Do I see LLM generated code as equivalent to me digging a hole with a shovel, it depends. Sometimes there was very little shovelling, other times there was no me involved and you may as well credit the entire hole to the shovel.
Where this will come in is when it comes to copyright and licensing.
If your entire product is LLM generated you sure as hell have no right to place any license on there other than potentially a MIT equivalent license, even that is dubious though but from an organisational standpoint MIT probably will be more widely accepted than saying it is uncopyrightable.
My argument being I would rather know that you didn’t even look at the code, which is what this will achieve, whether I agree with it or not at the very least it will make it easier to sift through the garbage.
The solution isn't to add notices to non-copyrighted things; it's to require notice for copyrighted things, including date.
Individually, of course, one should simply assume things are not copyrighted if you have no way to know, and do whatever you want. If the author can't be bothered to tell you, you have no moral responsibility to care.
Something you’ve created from nothing because of the tool you’ve used to create it should not be allowed to be licensed?
Yes it’s the same as using a stock drum pattern in a drum machine, it is not copyrightable because no human was involved in any part of it.
If you have an idea and want rights to it then do it the old fashion way and pay a developer to do a commissioned work and you can have your copyright, heres the catch, that will cost a hell of a lot more than 100usd a month
I wouldn't be surprised that if you asked an AI to weite said contract it would add a clause regarding copyright ownership of all codr and will put the onus on the developer to prove ownership of all of it.
Effectively you could sue them if you ever get sued.
When it comes to copyright and licensing it's complicated and it's best to write the code by hand.
It explains the brevity and any typos. That's how I see it used.