From Clawdbot to Moltbot to OpenClaw: The Full Naming History
From Clawdbot to Moltbot to OpenClaw: The Full Naming History
OpenClaw is one of the most-starred open-source projects on GitHub, but the name you know today is its third. The project rebranded twice in a matter of days, driven by a trademark dispute, a community that grew faster than anyone planned, and a maintainer who cared more about the code than the label on it. The naming saga is a small story with a big lesson about building an identity in the open. Here is how it actually unfolded, and why the chaos turned out to be a feature rather than a bug.
What was OpenClaw originally called?
OpenClaw was originally called Clawdbot when it launched in late 2025, then briefly Moltbot, before settling on OpenClaw. The three names map cleanly onto three phases of the project's early life: an enthusiastic launch, a forced legal pivot, and a final rebrand the community could rally behind. Each change happened under real pressure and on a compressed timeline, which is exactly why the story is worth telling rather than glossing over.
| Phase | Name | Driver |
|---|---|---|
| Launch | Clawdbot | Original release — a lobster-flavored nod to a popular AI assistant |
| Forced pivot | Moltbot | Trademark complaint pushed a rename away from the original |
| Final rebrand | OpenClaw | "Open" for open-source, "Claw" to keep the lobster heritage |
Chapter 1: Clawdbot, the enthusiastic launch
Clawdbot began as an open-source, self-hostable AI assistant released by an independent developer with a track record of shipping well-loved developer tools. The pitch was simple and timely: instead of renting access to someone else's assistant, you could run your own on your own infrastructure, with your own data staying under your control.
The name was a wink. It leaned on the lobster theme that would define the project's whole personality, paired with "bot" to make the purpose obvious. It was the kind of name that does real work: memorable, a little cheeky, easy to say in a Discord channel. Combined with the genuine appeal of self-hosting an AI assistant, that personality helped the project spread quickly. Developers liked the idea, liked the branding, and liked that they could kick the tires without signing up for anything.
For a while, everything pointed up and to the right. Then the legal questions arrived, and a clever name became a liability.
Chapter 2: Moltbot, the forced pivot
The second name, Moltbot, came out of a trademark complaint that the original name sat too close to an existing brand. Rather than fight an expensive and distracting legal battle, the maintainer chose to rename quickly and keep momentum.
Moltbot was a thoughtful attempt to preserve continuity. Molting is how lobsters shed their old shell to grow a larger one, which is an almost too-perfect metaphor for a project outgrowing its first identity. The biology nerds appreciated it. The lobster theme survived. On paper, it worked.
In practice, the reception was mixed. Some people loved the cleverness; others found the word clunky to say and harder to build a brand around. The internet did what the internet does and produced its share of jokes. But the substance underneath the name had not changed at all. The code was the same, the community was the same, and the value proposition was the same. A name, the thinking went, is just a name.
That conviction was about to be tested again, faster than anyone expected.
Chapter 3: OpenClaw, the name that stuck
The third and final name, OpenClaw, replaced Moltbot only days later, and this one held. The logic was direct and easy to defend: "Open" signals the open-source, community-driven nature of the project, and "Claw" preserves the lobster heritage the community had embraced from the very first release.
What made OpenClaw work where Moltbot stumbled was clarity. It reads as professional without being sterile. It tells you something true about the project the moment you hear it. It carries no awkward phonetics and no trademark baggage. The community adopted it almost immediately, and within a short time it became the only name anyone used. The earlier names survive mostly as trivia and as stray references buried in old forks and descriptions, fossils from a very fast evolution.
Why the naming saga actually matters
The naming saga matters because it is a compact case study in how to handle a brand crisis in open source without losing the community. A few lessons stand out.
- Speed beats stubbornness. Dragging out a trademark fight would have burned goodwill and attention. Moving fast, even imperfectly, kept the focus on the work.
- Identity lives in the community, not the wordmark. Through two renames, the people stayed. The lobster motif persisted because users wanted it to, not because a style guide enforced it.
- A forced constraint can produce a better result. The original name was good. The final one is arguably better: clearer, more durable, and more honest about what the project is. Constraints often do that.
- Not being precious is a leadership skill. Caring more about the project than about your own first idea is exactly what let the rebrand happen cleanly.
For anyone building in the open, the takeaway is reassuring. Getting the name wrong, even twice, is survivable. What is not survivable is freezing up, picking fights you cannot win, or treating the brand as more important than the people and code behind it.
Why naming is so hard for open-source projects
Naming is uniquely hard for open-source projects because the name has to clear a trademark bar, survive public scrutiny, and stick in a community's vocabulary all at once, often before anyone realizes the project will matter. A commercial product usually gets a name vetted by lawyers and marketers before launch. An open-source project frequently gets its name from whatever its creator typed into a repository on a quiet evening, and only discovers the consequences after it goes viral.
OpenClaw's journey illustrates each of the pressures that make this so fraught.
- Legal exposure scales with success. A name no one notices is a name no one challenges. The moment a project gets popular, it becomes visible to the holders of similar trademarks, and the very growth that validates the work also invites the dispute. Clawdbot was fine until it was famous.
- The community owns the vocabulary, not the maintainer. A name is only real once people use it in conversation, in issues, in tutorials, and in their own projects. That is a strength and a constraint: a maintainer can announce a new name, but the community decides whether it sticks. Moltbot was technically the project's name for a few days and never truly became the word people reached for.
- Heritage and clarity pull in different directions. Communities form attachments fast. The lobster motif became identity almost immediately, so any new name had to honor it or risk feeling like a betrayal. At the same time, the name needed to be clean, professional, and unambiguous. OpenClaw worked because it satisfied both pulls at once, which is rarer than it sounds.
The practical lesson for builders is to pick a name you can defend, both legally and in a community's mouth, and to hold it loosely enough that you can change it without ego if reality demands it. The projects that handle a forced rename well are the ones that treat the name as a label for the work rather than the work itself.
The lobster that refused to leave
One detail makes the whole saga more than a legal footnote: through two renames and a trademark fight, the lobster stayed. That persistence is the real story. Branding that a team merely imposes tends to evaporate the moment it becomes inconvenient. Branding that a community genuinely adopts behaves differently, because it lives in thousands of small places no announcement controls, the in-jokes, the avatars, the way people talk about the project to their friends. The shell could be renamed; the creature inside it could not. That is exactly why the final name kept the claw, and exactly why it stuck where a cleaner break would have failed.
Frequently asked questions
Did the name changes hurt the project?
Not in any lasting way. The renames created short-term confusion and a wave of jokes, but the underlying value proposition, a self-hostable AI assistant you fully control, never changed. The community stayed through both transitions, which is the clearest evidence that people were there for the work rather than the wordmark.
Why did Clawdbot have to change its name?
Clawdbot changed because of a trademark complaint that the name was too close to an existing brand. Rather than litigate, the project chose to rename and keep its energy pointed at development and community instead of legal defense.
How long did the name Moltbot last?
Moltbot was short-lived, replaced by OpenClaw within days. It served as a transitional name during a fast-moving rebrand rather than a long-term identity.
What does the "Claw" in OpenClaw refer to?
The "Claw" preserves the lobster theme that defined the project from its first release. "Open" was added to emphasize its open-source, community-driven character, giving the final name both heritage and clarity.
Is the lobster branding official or a community thing?
It is both. The theme started with the project's founder and was enthusiastically adopted by the community, which is precisely why it survived two name changes intact.
What myHermy has to do with the story
myHermy exists because OpenClaw exists. We built a platform that lets you deploy your own OpenClaw instance without wrestling a terminal, hand-editing config files, or learning DevOps along the way. The naming journey shaped how we think about our own product: keep it simple, keep it honest, and do not make people decode clever wordplay to understand what they are getting.
So here is the plain version. myHermy gives you a dedicated OpenClaw VPS with root SSH, daily backups, and OAuth subscription bridging so you can reuse plans like ChatGPT Plus, Claude Max, GitHub Copilot, or SuperGrok instead of paying API rates on top of hosting. If you already run OpenClaw elsewhere, our migration path brings it over. Plans start at $19/mo. See how we compare on the OpenClaw alternative page, or deploy from the myHermy home page.
The project took three tries to land its name. We only needed one promise: myHermy hosts your Claw. One click. Done.