What was spotted
Users of Meta’s Muse assistant noticed that its workspace filenames matched those used by OpenClaw, the open-source agent project, and that Muse carried a SOUL.md configuration file with nearly identical content. That file defines an agent’s personality, communication style, values and behavioural boundaries — the part of an agent product that is least a technical artefact and most a set of authored choices.
TechCrunch reported on Tuesday that Meta did not dispute the resemblance.
Meta’s answer
Nat Friedman, head of product at Meta’s Superintelligence Labs and formerly chief executive of GitHub, said on X that Muse was “heavily inspired as a product by OpenClaw” while maintaining that Muse itself was “built from scratch.”
He explained that the team “fell in love with using OpenClaw” after January 2026 and wanted to build something like it that could scale to billions of users while being safe and secure. Of the specific design choices, he said: “we thought that Peter got those things exactly right” — a reference to Peter Steinberger, OpenClaw’s creator, who was hired by OpenAI earlier this year after the tool went viral.
Inspiration, copying and licences
The distinction Friedman is drawing — inspired by the product, written from scratch — is the one that matters legally, and it is also the one that is hardest to check from outside. Nobody has alleged that Meta lifted OpenClaw’s source. What users found was the shape of the thing: the same files in the same places, doing the same jobs, with near-identical text in the file that sets the agent’s character.
Open-source licences govern code. They do not govern conventions, file layouts or the idea that an agent should have a personality file, and in practice that is where most of the differentiation in agent products currently sits.
Why this keeps happening
Agent design is converging fast because the design space is small and a few conventions have proved they work. A markdown file describing who the agent is; a workspace directory the agent can read and write; tools declared in a manifest. Once one project gets that right and thousands of developers learn it, a company shipping to billions of users has an incentive to match the convention rather than invent a competing one.
What is unusual here is the candour. Meta could have said nothing; instead its product head named the project, named its creator and said he got it right.
What to watch
Whether OpenClaw’s maintainers respond, and whether the convention hardens into something more formal. Config formats that several vendors copy tend to end up as de facto standards, and the question then is who gets to change them.
