Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Who owns the code Claude Code wrote?

legallayer.substack.com

Post reply on HN
Print view View original

61–70 of 570 posts

Re: Who owns the code Claude Code wrote?

#61

Post by senaevren »

jugg1es wrote: post #4

I want this question to have an interesting answer, but everyone knows that if this question ever goes to the courts, ownership will go to the people in charge with the money. The idea that Anthropic may not own Claude Code just because Claude wrote it is wishful thinking.

The work-for-hire doctrine actually supports your intuition more than the AI authorship question does. The reason Anthropic likely owns Claude Code has little to do with whether Claude wrote it and everything to do with the employment contracts of the engineers who directed it. The DMCA takedown question is genuinely interesting though because DMCA requires the claimant to assert copyright ownership in good faith. If a court later found the codebase was predominantly AI-authored and therefore not copyrightable, the 8,000 takedowns could be challenged as bad faith DMCA claims. That is a different and more tractable legal question than the ownership one.

Re: Who owns the code Claude Code wrote?

#62

Post by senaevren »

smashed wrote: post #38
conartist6 wrote: post #18

Earlier quoted context omitted.

It is copyrightable. A *human* can copyright code they wrote.

I meant in the sense that the "tool" is an LLM and the "work" was vibe coded. If vibe coded work is not copyrightable, it cannot be reassigned to the employer and become copyright protected.

This is the sharpest point in the thread. You are right if the output has no copyright to begin with, there is nothing to assign. The employer's contractual claim over purely AI-generated code is not a copyright claim, it is a trade secret and confidentiality claim. Those are weaker protections: they require the information to remain secret, they do not survive disclosure, and they cannot be enforced against independent creation of the same code. Most IP assignment clauses in employment contracts were not drafted with this scenario in mind and may be claiming rights that do not legally exist.

Re: Who owns the code Claude Code wrote?

#63

Post by senaevren »

_flux wrote: post #21

I think it should be pretty clear that if you provided the tool the specification for the code you want, you have already provided creative input. After all, is this not what happens with compilers as well? LLM agents are just quite advanced compilers that don't require the specification to be as detailed as with traditional compilers.

The compiler analogy is the right one to reach for and the Copyright Office addressed it directly: the question is not whether you provided input, it is whether the creative expression in the output reflects human authorship. With a traditional compiler, the programmer authors every expression in the source. With an LLM, the programmer authors the intent and the model makes the expressive decisions about structure, naming, pattern, and implementation. Whether that distinction matters legally is what Allen v. Perlmutter is working through right now. The summary judgment briefing completed in early 2026 and it may be the next landmark ruling on exactly this question.

Re: Who owns the code Claude Code wrote?

#64

Post by senaevren »

palata wrote: post #53

One question I have is this: if an employee produces code predominantly generated by AI, it means that it is not copyrightable. Does that mean that the employee can take that code and publish it on the Internet? Or is it still IP even if it is not copyrightable? That would feel weird: if it's in the public domain, then it's not IP, is it?

That is exactly the right question and the answer is genuinely strange. Uncopyrightable work falls into the public domain, which means anyone can use it, copy it, or build on it freely. The employer can still call it a trade secret and protect it through confidentiality obligations in employment contracts, but that protection is contractual rather than property-based. A trade secret loses protection the moment it is disclosed. So the employer's claim over purely AI-generated code is essentially: "you cannot share this" rather than "we own this." Those are meaningfully different legal positions, and most companies have not thought through which one they actually have.

Re: Who owns the code Claude Code wrote?

#66

Post by senaevren »

bko wrote: post #44
freedomben wrote: post #20

Earlier quoted context omitted.

> Almost no one thinks their code is copyrightable or seriously thinks their code is a moat. You'd be surprised! Among non-software management types, they often think of the code as extremely valuable IP and a trade secret. I'm a CTO and I've made comments before to non/less technical peers about how the code (generally speaking) isn't that big of a secret, and I routinely get shocked expressions. In one case the com…

You're right, I guess maybe I mean in any serious actionable way. Senior, non technical people leave plenty of money on the table by thinking they're protecting something valuable or they have some kind of secret sauce. It's all silly is what I meant to say, and digging into the technicalities of whether your code is truly copyrightable is kind of pointless. It's all vibes.

The place where it concretely matters is M&A due diligence. Acquirers are now routinely asking about AI tool usage in development and running license scans as a condition of closing. A codebase that cannot demonstrate human authorship over its core IP, or that contains GPL contamination, creates a representation and warranty problem in the purchase agreement. For most companies day to day you are right. For the companies that get acquired or raise institutional capital, the question becomes very concrete very quickly.

Re: Who owns the code Claude Code wrote?

#68

Post by senaevren »

p0w3n3d wrote: post #40

That's quite impressive approach from the companies' perspective. Let's first use claude code and then we'll think who the code belongs to. I think that the gold rush approach happening right now around me (my company EMs forcing me to work with claude as fast as possible) show really short-sight of all the management people. First - I lose my understanding of the code base by relying too much on claude code. Second…

The fourth point about code commenting is the one that connects directly to the ownership question. When developers write comments to explain intent, those comments are evidence of human creative direction. When Claude writes the code and the comments, and the developer merges without adding their own explanation of the architectural decisions, the record of human authorship disappears along with the institutional knowledge. The documentation problem and the copyright problem are the same problem.

Re: Who owns the code Claude Code wrote?

#69

Post by TheFirstNubian »

The elephant in the room, of course, is what constitutes “meaningful human authorship.” However, I cannot shake off the feeling that all user interactions with these AI models are being logged. Perhaps this may turn out to be the bigger concern in a potential legal battle than code authorship.

Re: Who owns the code Claude Code wrote?

#70

Post by senaevren »

embedding-shape wrote: post #31
e12e wrote: post #28

Seems to gloss over other kinds of contamination, beyond GPL code. Code from pirated text books, the problem with the entire language model being trained on copyright data, and on the possibility of the training data containing various copyrighted code.

> Code from pirated text books Anthropic "solved" this by intermingling the texts extracted from pirated books (illegal) with texts extracted from the physical books they bought and destroyed (legal), so no one can clearly say if the copyrighted material it spits out came from a legal source or not. Everyone rejoiced.

The intermingling argument is actually central to the Bartz settlement structure. The settlement required destruction of the pirated dataset specifically because commingled training data creates an unresolvable provenance problem. For deployers building on Claude, EDPB Opinion 28/2024 requires a documented assessment of the foundation model's training data legal basis before deployment. "We cannot tell which outputs came from which source" is not a satisfactory answer to a regulator running that assessment. wrote about it before here: https://legallayer.substack.com/p/i-read-every-edpb-document...
Post reply on HN