클로드 코드가 작성한 코드의 저작권은 누구의 것인가?

Who Owns the Code Claude Wrote? AI-generated code copyright explained for builders. Sena Evren Apr 28, 2026 2 2 Share TL; DR Agentic coding tools like Claude Code, Cursor, and Codex generate code that may be uncopyrightable, owned by your employer, or contaminated by open source licenses you cannot see. If you are shipping AI-assisted code and have not thought about any of this, this piece is for you. Legal Layer Angle: In this piece I will talk about what a developer using AI coding tools needs to document to own what they build, what their employment contract probably says about AI-assisted work product, and what the practical implication is for open source contributions written with AI assistance. If you shipped code this week, some of it was probably written by an AI. The question of who legally owns that code is less settled than most developers assume, and the answer depends on three things that have nothing to do with how good the code is: whether a human made enough creative decisions to establish copyright, whether your employment contract already assigned it to your employer, and whether the model pulled from GPL-licensed training data and quietly contaminated your codebase. On March 31, 2026, Anthropic accidentally published 512,000 lines of Claude Code’s source code in a routine software update through a missing configuration file. Before sunrise, the codebase was mirrored across GitHub. Before breakfast, a developer had used an AI tool to rewrite the entire thing in Python, and the “claw-code” repository hit 100,000 GitHub stars in a single day, the fastest in history. Then came the DMCA takedowns, and then came the question nobody had a clean answer to: If Claude Code was, by Anthropic’s own lead engineer’s admission, predominantly written by Claude itself, does Anthropic even own it? Can you issue a DMCA takedown for code that copyright law may not protect? That incident compressed every open question about AI-generated code ownership into a single news cycle. The same questions apply to your codebase. The copyright rule nobody told you Here is the legal baseline, in plain terms: copyright only protects work created by a human. The US Copyright Office confirmed this in January 2025, and the Supreme Court declined to disturb it in March 2026 when it turned away the Thaler appeal. Works predominantly generated by AI without meaningful human authorship are not eligible for copyright protection, and that rule is now settled at the highest judicial level available. What it means for you: Code that Claude Code or Cursor generated and you accepted without meaningful modification may not be copyrightable by anyone. If a competitor copies it, you may have no legal recourse, because the code sits in the public domain in everything but name. The phrase that determines whether your code is protected is “ meaningful human authorship ,” and the Copyright Office has deliberately refused to quantify it with a percentage or a number of edits, because what courts look for is evidence that a human made genuine creative decisions: choosing the architecture, deciding what to reject, restructuring the output to fit a specific design. Specifying an objective to the model is not enough. Directing how the work is constructed is what counts. In an agentic workflow, this distinction is harder to establish than it sounds. Consider a typical Claude Code session: You write a one-line prompt: “build a rate limiting module for the API” Claude Code plans the approach, generates five files, and iterates through three versions You review the output, run the tests, and merge Your contribution in that sequence is your architectural intent and your final approval. Whether that constitutes meaningful human authorship in a courtroom is an unresolved question with no definitive court ruling yet. The honest answer is: probably yes for modules you substantially redirected, probably no for code you accepted verbatim, and unclear for everything in between. What your employer probably already owns Before you think about whether your code is copyrightable, there is a more immediate question: even if it is, is it actually yours? Your employment contract almost certainly says that anything you build at work belongs to your employer. That principle has a name in copyright law: the work-for-hire doctrine. Under it, any code created by an employee within the scope of their employment is owned by the employer, who is treated as the legal author, regardless of whether the code was written by hand, generated by Claude Code, or some combination. Using an AI coding tool during work hours, on a work project, on a work machine, does not change who owns the result. Most employment contracts go further than the doctrine’s defaults. Look for a section in yours called “Intellectual Property,” “IP Assignment,” or “Work Product.” Open the contract, search for those terms, and read that section. A clause that says any of the following almost certainly covers your AI-assisted code: “any work product created using company equipment or resources” “any invention or development made during the term of employment” “any software created with the assistance of company-licensed tools” The third one is the one to watch. If your employer licenses Claude Code, Cursor, or Copilot for the team, and you use those same tools to build a side project, a broad IP assignment clause may give the employer a claim over that project, even if you built it on your own time. A senior developer in San Francisco described exactly this situation earlier this year. He had used Claude Code for work projects and for a personal fitness tracking app built on evenings and weekends. His company updated its IP policy and claimed everything he had built with AI assistance, including the personal app, arguing that because Claude had access to open work files in the IDE, any AI output was a derivative work of company IP. The argument does not hold up legally, because context visibility in an IDE does not make AI output a derivative work of files that were open nearby, and the connection between what Claude can see and what it generates is probabilistic pattern completion, not copying. But the argument illustrates what employers are starting to claim. If the clause is broad enough, it has surface validity regardless of what the AI actually did. The practical rule: if you are building something on the side, use a personal account, a personal machine, and tools you pay for yourself. Keep your employer’s licensed tools out of that workflow entirely. The open source contamination problem Even if you own your AI-generated code, you may have already contaminated it with an open source license you cannot see. AI coding tools are trained on massive amounts of public code, including code licensed under the GPL, LGPL, and other copyleft licenses. Copyleft licenses carry a specific obligation that travels with the code: If you distribute software that is a derivative of GPL-licensed code, you must release your own source code under the same license This applies even if you did not know the code you incorporated was GPL-licensed “I did not know” is not a defense to a copyleft violation 🚨 When an AI tool generates code that closely resembles GPL-licensed code from its training data, and you ship that code in a commercial product without releasing source, you may have created a copyleft violation without ever touching the original repository. The chardet dispute made this concrete in early 2026. A developer used Claude to rewrite chardet, a Python character encoding library, and re-released it under an MIT license, arguing that the AI rewrite was a “clean room” implementation free of the original LGPL license. The legal question the community fought over: if Claude was trained on the LGPL-licensed codebase and its output reflects patterns learned from that code, can the output be treated as license-free? The emerging legal consensus is probably not, an