Copilot's DMCA win moves the notice-stripping question onto the developer who ships the code
A unanimous Ninth Circuit panel held that Copilot generates code instead of retrieving files, so the DMCA claim in Doe v GitHub is out. The two breach-of-contract claims against GitHub, Microsoft and OpenAI are still running.
The Product Desk
What happened
- A unanimous Ninth Circuit panel affirmed the dismissal of the DMCA section 1202(b) claim in Doe v GitHub, number 24-7700, in an opinion issued Wednesday by Judge Eric Miller.
- The plaintiffs are anonymous programmers who publish open-source code and sued GitHub, Microsoft and OpenAI, arguing that Copilot and Codex reproduce their code without attribution.
- On the certified question of identicality, the panel called the label something of a misnomer and said the DMCA does not demand literal sameness between the two works.
- The plaintiffs cleared standing partly on GitHub's own duplicate-detection filter, which blocks suggestions matching public code at verbatim snippets of 150 characters or more.
Why it matters
- Who's exposed exposure The reasoning covers whoever generated the completion, so the person newly carrying the notice-stripping risk is the developer who commits a substantial reproduction of somebody else's file without its header.
- What it limits constraint Turning the duplicate-detection filter off is harder to defend in an internal review now that a federal court has cited the filter's existence as evidence that identical output happens.
- Who has to decide decision Legal review of coding assistants has to move onto licence text and the vendor terms a team accepted, because contract is what is left of this case.
- What it sets up precedent A vendor that cites this opinion for comfort about training sets is citing a question the panel refused to answer, so the training fight starts fresh in front of the next court.
Next story · Invest · 3d ago
SPUR's 80-plus publishers can count AI use of their news only where AI firms agree to report itConfirmed3 publishers
Copyright management information in open-source code sits in a header at the top of the file: the author's name, the copyright notice, the licence terms [13]. Section 1202(b) makes it unlawful to intentionally remove or alter that header [13]. So the practical question inside a pull request is how a header goes missing.
The Ninth Circuit answered it by asking where the text came from. A search engine retrieves and displays stored information, meaning copies of things that already exist [6]. By the programmers' own account, Copilot predicts a likely completion from statistical patterns, and the panel read that as generation [8]. "One who creates a new work and fails to include CMI cannot be said to have 'removed' or 'altered' anything," the opinion says [5]. Judge Eric Miller added that "If Copilot functioned like a search engine and produced outputs that were identical to plaintiffs' code but did not contain CMI, then plaintiffs might have a stronger claim" [7].
That is a holding about the tool, not about the commit that follows. The defendants conceded that two works need not be identical, the panel agreed, and Miller wrote that minor cosmetic changes will not protect someone who substantially reproduces a work and strips the notice [15]. A completion long enough to be a substantial reproduction of a real file, accepted and pushed without the header the original carried, lands inside that description [20]. GitHub generated the text and your repository holds the copy [20].
What is left of Doe v GitHub is contract. Two breach-of-contract claims against GitHub, Microsoft and OpenAI are still running [4]. The programmers' other theory, that the defendants stripped notices from the code before feeding it into training, never got decided, because the panel held it forfeited [9]. At the hearing on the first motion to dismiss, the district court asked whether copying training data into Copilot breached the licences' attribution requirement, and counsel for the programmers answered "Perhaps it doesn't." [10] The judge then observed that the "complaint is not about training. It just isn't." [11] A later order recorded that the "Plaintiffs do not allege they were injured by Defendants' use of licensed code as training data", and nobody corrected it, orally or in writing [12].
For a team rolling these tools out, the review is two questions per repository. One is whether anything being shipped reproduces a substantial part of a file somebody else wrote. The other is whether that file's licence required a name or a notice the commit did not carry over. Both answers show up in a diff, which is where the header lives [13]. The statutory route through the vendor is closed [2], and the licence obligation stays with whoever redistributes the file [20].
Miller was candid that the statute's own authorities come from print media, such as defacing the title page of a book, and that they "do not map neatly onto the emerging digital technologies like artificial intelligence to which the DMCA's protections also apply" [16]. He also wrote, for the panel, that it declined "plaintiffs' invitation to transform run-of-the-mill copyright-infringement claims into DMCA claims" [2].
What to watch
- Whether the programmers can produce actual evidence of verbatim output at summary judgment, which the panel said the pleading stage did not require.
- Whether the two surviving breach-of-contract claims produce a ruling that treats open-source attribution clauses as enforceable contract terms.
- Whether a later plaintiff preserves the input theory about stripping notices from training data that this panel held forfeited.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence84
- Adoption
- Not scored
- Hype gap+10
- Incentives70
- Confidence76
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
The Ninth Circuit issued its opinion in Doe v GitHub, number 24-7700, on Wednesday, and a unanimous panel affirmed the dismissal of the plaintiffs' DMCA section 1202(b) claim.
- [2]
"We decline plaintiffs' invitation to transform run-of-the-mill copyright-infringement claims into DMCA claims," Judge Eric Miller wrote for a unanimous Ninth Circuit panel.
- [3]
Anonymous programmers who publish open-source code sued GitHub, Microsoft and OpenAI over Copilot and Codex, arguing the tools reproduce their code without attribution in breach of section 1202(b) of the Digital Millennium Copyright Act.
- [4]
The ruling leaves the plaintiffs' two breach-of-contract claims running.
- [5]
"One who creates a new work and fails to include CMI cannot be said to have 'removed' or 'altered' anything," the opinion says.
- [6]
The court's comparison was to a search engine, which retrieves and displays stored information, meaning copies of things that already exist.
- [7]
"If Copilot functioned like a search engine and produced outputs that were identical to plaintiffs' code but did not contain CMI, then plaintiffs might have a stronger claim," Miller wrote. "But that is not what plaintiffs have alleged."
- [8]
By the programmers' own account Copilot predicts a likely completion from statistical patterns, and the court took that as describing generation rather than retrieval.
- [9]
The panel decided only the output theory and held the input theory, that the defendants stripped notices from the code before feeding it into training, forfeited, so it never reached the training-data question.
- [10]
Asked at the hearing on the first motion to dismiss whether copying training data into Copilot breached the licences' attribution requirement, counsel for the programmers answered "Perhaps it doesn't."
- [11]
The district judge observed that the "complaint is not about training. It just isn't."
- [12]
A later district court order stated that the "Plaintiffs do not allege they were injured by Defendants' use of licensed code as training data", and nobody corrected it, orally or in writing.
- [13]
Section 1202(b) bars intentionally removing or altering copyright management information, meaning the author's name, the copyright notice and the licence terms, which in open-source code sits in a header at the top of the file.
- [14]
The certified question was whether section 1202(b) carries an identicality requirement; the panel said "identicality" is "something of a misnomer", that the DMCA does not demand literal sameness, and that the label is a gloss on the statutory words rather than a separate element.
- [15]
The defendants conceded that two works need not be identical, the court agreed, and minor cosmetic changes will not protect someone who substantially reproduces a work and strips the notice.
- [16]
The opinion concedes its authorities come from print media, such as defacing the title page of a book, and that those "do not map neatly onto the emerging digital technologies like artificial intelligence to which the DMCA's protections also apply", Miller wrote.
- [17]
The defendants argued the programmers could not show their own code was at risk; the panel disagreed, noting the complaint cites academic research finding that large language models will sometimes "emit the memorized training data verbatim", a phenomenon that "will likely get worse as models continue[] to scale".
- [18]
GitHub's duplicate-detection feature lets users block suggestions matching public code at verbatim snippets of 150 characters or more, and the court treated the existence of that filter as some evidence that Copilot does emit identical copies.
- [19]
The panel was explicit that the pleading stage was enough for now and that at summary judgment the programmers would have to produce actual evidence.
- [20]
The opinion's safe reasoning covers the party that generates a new completion, while the party that substantially reproduces an existing file and omits its notice remains within the conduct the panel described as actionable.
Sources
2 independent publishers whose own reporting we read for this story.
- devops.comUS District Court Decision in AI’s Favor Worries Open-Source Developers
1 article · September 18, 2026
- thenextweb.comCoders lose their DMCA case against GitHub Copilot and Codex
1 article · September 18, 2026
Topics and entities
Topics
- Open-source licence compliance
- AI coding assistants
- AI Copyright Litigation
- Copyright management information