Who Gets Credit for Scion? Anthropic, Mononoke, and the Missing Link
Scion
Anthropic's internal version-control system.
Mononoke
The server component of Meta's Sapling source-control system.
derived data
Extra information computed from change records to answer history questions.
What happened
Anthropic, the AI company behind Claude, published a post on Oct. 13 about Scion. Scion is Anthropic's internal version-control system. It was designed for a very large code repository and many always-online agents. The official post described a different approach from Git. Anthropic's official post
On Oct. 14, a developer who helped build Mononoke at Meta published a comparison. Mononoke is the server component of Meta's Sapling source-control system. The author said Scion's design closely resembled Mononoke. The author had described similar ideas in 2022 materials. The complaint was not that open-source design may never be reused. It was that Anthropic named Sapling, but did not name Mononoke. The author called the omission close to plagiarism. The original comparison
The story received 416 points and 156 comments on Hacker News. Those numbers show community attention. They do not prove the claim. Hacker News discussion
The technical background
Version control records changes to code. It helps people compare revisions and trace file history. Scion stores a record of each change. It then creates derived data, or extra information, for file history and line authorship. The author's older description of Mononoke used a similar idea. That similarity explains the dispute, but it is not an independent finding of copying.
Anthropic says its need for Scion grew with its coding workload. Merged changes rose from about 2,500 per day in May 2026 to more than 30,000 in September. Main-branch history approached 100 gigabytes. CI and other jobs performed about 25 million checkouts each day. Anthropic says it built and migrated to Scion in five months.
The original official post named Google's Piper and Meta's Sapling as prior art. On Oct. 15, Anthropic updated the post. A footnote now says Mononoke is Sapling's server component. It also says the Bonsai data model pioneered many techniques used in Scion.
Why the credit matters
The author does not object to reusing an open-source design. Open source exists partly so useful ideas can spread. The request is for clearer credit. Readers should be able to see which earlier system shaped a new one.
AI-assisted design makes that trail harder to see. An AI can study public code and suggest a familiar architecture. A polished announcement can make an old idea sound newly invented. Teams therefore need to separate independent invention, ordinary reuse, and direct imitation. A short post cannot settle those categories by itself.
What we can confirm
Anthropic publicly described Scion and cited Piper and Sapling. After the update, it also named Mononoke and Bonsai. The individual comparison points to similar structures and terms in older Mononoke materials. The Hacker News score shows that the topic attracted attention. It does not establish who is right.
What remains unknown
The public material does not show the exact code overlap. It does not show which design decisions came first. It does not say what materials Claude saw, if any, while helping with Scion. It also does not settle whether Anthropic's Sapling credit was meant to cover Mononoke. No legal conclusion follows from these posts alone.
What to watch next
The next useful evidence would be a detailed, independent comparison. Clearer attribution from Anthropic would also matter. More broadly, AI-assisted engineering will need better records of public projects and earlier ideas. The lasting question is not only whether Scion works well. It is whether teams can explain where its ideas came from.
A credit dispute over Anthropic's Scion
📰 Full story: Who Gets Credit for Scion? Anthropic, Mononoke, and the Missing Link
A new code tool looks close to an older system. The bigger question is how teams credit earlier work.
Scion
Anthropic's internal tool for managing code changes.
Mononoke
An older source-control server made at Meta.
derived data
Extra information made from code-change records.
💡 The gist
- Anthropic, the company behind Claude, built Scion.
- Mononoke is Meta's older source-control server.
- A builder says Scion resembles it closely.
Anthropic introduced Scion on October 13. Scion is an internal tool. It manages changes in a very large codebase.
A developer who helped build Mononoke compared the designs. Mononoke is part of Meta's Sapling system. The developer described similar ideas in 2022 notes. Those ideas involve making extra information from code changes.
Scion uses this information for history questions. This extra information is called derived data. It can help show who changed a line. It can also help find a file's earlier paths.
Anthropic first named Sapling as earlier work. It later updated the post. The update named Mononoke in a footnote. It called Mononoke the server part of Sapling. It also mentioned the Bonsai data model.
The issue is not simply whether reuse is allowed. Open-source projects are made to be reused. Credit helps readers follow an idea's path. AI tools make this harder. They can study public projects and suggest designs that already exist.
We still do not know the exact amount of overlap. We do not know what Claude saw. We do not know how each design choice was made. So this is not a final finding of plagiarism.
The story reached 416 points and 156 comments on Hacker News. That shows attention. It does not prove the claim.
💬 An easier summary of the Scion–Mononoke debate
The main question is less whether Anthropic may reuse an idea and more whether it clearly named the older system it resembles.
- The article's author is not objecting to using Mononoke's ideas. The complaint is that Scion's design and vocabulary look very similar, so Mononoke should be named openly as prior work.
- The defense is that Anthropic already mentioned Piper and Sapling, and commenters describe Mononoke as part of Sapling. Some also argue that an independent rewrite of similar functionality is allowed and that extra credit is not legally required.
- Because AI can learn and reproduce older designs, some commenters want the builders to search for earlier work and cite it. Others say patent and copyright risks can make companies tell engineers not to search for prior art.
- A very large monorepo may need a different VCS, or version-control system, because Git can struggle with many merges. Google and Meta reportedly faced similar problems more than 10 years ago, while the claim that Anthropic is below one commit per second is only a commenter's estimate.
- Some people think the announcement mixes a real scaling problem with IPO marketing. The comparison of roughly 60,000 Google engineers and perhaps 2,000 Anthropic engineers is also a commenter estimate, not a verified number.
initial digest at 156 comments (revision 1). We fetched 100 comments and sampled 100 across the thread. These are HN users’ reports, not independently verified facts.
A New Code Tool Looks Like an Older One
📰 Full story: Who Gets Credit for Scion? Anthropic, Mononoke, and the Missing Link
Anthropic showed a new tool. Someone said it looks like an older tool.
Scion
A tool that remembers changes in code.
Mononoke
An older tool made at Meta for code changes.
Hacker News
A website where people discuss technology news.
Anthropic (the company that makes Claude) showed Scion. Scion is a tool for remembering code changes.
Mononoke (a tool made at Meta) is older. A Mononoke builder said Scion looks very similar.
Anthropic first mentioned Sapling, Mononoke's larger system. Later, Anthropic added Mononoke's name.
We still do not know how much matches. Similar does not automatically mean copying.
Hacker News gave the story 416 points and 156 comments. That shows attention. It does not prove the claim.
The bigger question is simple. When AI helps make something new, who gets credit? Clear names help people follow an idea.
💬 Scion and Mononoke in very simple terms
Anthropic made a new tool for storing code, and people noticed that it looks a lot like an older open-source tool.
- The new tool is called Scion. Some people say its design and words are very close to Mononoke. They want Anthropic to say Mononoke's name.
- Other people say that mentioning Sapling is enough because Mononoke is part of Sapling. They also say that making a similar tool independently can be allowed, so this is mostly a question of giving credit.
- AI can repeat old ideas, so some people want builders to check where ideas came from. Others say legal worries can make checking old work risky.
- Big code boxes can be hard for Git to handle. Some people say Anthropic has a real problem; others think the announcement also helps its IPO story. One commenter guessed the company had fewer than one code change per second, and guessed Google had about 60,000 engineers versus about 2,000 at Anthropic; those are only guesses.
initial digest at 156 comments (revision 1). We fetched 100 comments and sampled 100 across the thread. These are HN users’ reports, not independently verified facts.
💬 The HN debate over Scion and Mononoke
HN commenters disagree about how closely Scion follows Mononoke, whether citing Sapling is enough, how AI changes attribution norms, and whether Anthropic truly needed a new VCS.
initial digest at 156 comments (revision 1). We fetched 100 comments and sampled 100 across the thread. These are HN users’ reports, not independently verified facts.