Community Guide

History of OpenClaw

The timeline from ClawdBot to OpenClaw, including the rename sequence, founder context, explosive growth, and governance shift.

Mar 13, 2026

Why the timeline matters

OpenClaw’s current shape only makes sense if you understand how quickly it grew. It went from a personal weekend project to one of the most visible repositories on GitHub in a matter of months.

That speed explains a lot:

why older sources still use different names
why governance questions appeared so early
why security pressure arrived almost immediately
why the project still feels founder-shaped even after it got much larger

The short timeline

November 2025

Peter Steinberger released the original weekend project as ClawdBot. The name referenced Claude, and the lobster theme was already there.

Mid-January 2026

Growth accelerated dramatically. The Orange Paper records a 72-hour burst of roughly 60,000 stars and days with about 9,000 new stars.

January 27, 2026

Anthropic trademark pressure forced a rename from ClawdBot to Moltbot.

January 30, 2026

The project was renamed again, this time to OpenClaw, emphasizing the open-source identity while keeping the lobster theme.

Early February 2026

Growth continued, but so did risk:

a major RCE issue entered the story
skills supply-chain attacks hit the ecosystem
Google account bans affected some users

February 14, 2026

Peter Steinberger announced that he was joining OpenAI. According to the Orange Paper, the project moved to foundation-style governance and remained independent even with OpenAI as a sponsor.

March 3, 2026

OpenClaw passed React in GitHub stars and briefly became the most-starred software project on GitHub.

March 9, 2026

The Orange Paper’s recommended stable snapshot moved to v2026.3.8, which emphasized security hardening, ACP identity features, and backup tooling.

ClawdBot, Moltbot, and OpenClaw are the same lineage

This sounds obvious once you know it, but it matters for search and source reading.

Older screenshots, community guides, GitHub threads, and social posts may still refer to:

ClawdBot
Moltbot
OpenClaw

Those are not three different products. They are the same project at different moments in its naming and governance story.

If you are reading older material, normalize the name first before you decide the source is outdated.

Why the renames mattered

The rename sequence was not cosmetic. It shows three things:

the project was growing faster than its governance and branding were originally designed for
the lobster identity survived every rename
“OpenClaw” is explicitly an open-source framing, not just a clever brand

Why founder context still matters

The founder story matters because OpenClaw still carries the shape of its origin.

The official README now describes OpenClaw as a personal AI assistant you run on your own devices, with the Gateway as the control plane rather than the whole product. That framing still feels founder-shaped:

local-first rather than cloud-first
operator tooling rather than glossy abstraction
one assistant spanning channels, tools, and devices
a strong bias toward inspectable files and CLI control

That is why OpenClaw often feels different from products that look more polished but less ownable.

Why the OpenAI moment mattered

The creator joining OpenAI triggered understandable skepticism, but the Orange Paper’s framing is more specific:

the project became foundation-operated
OpenAI was a sponsor, not the owner
the project remained independent

That does not eliminate ecosystem risk, but it does explain why “Is OpenClaw still independent?” became a common question.

How to read older sources correctly

If you are using community articles, early screenshots, or historical explainers, read them with these adjustments in mind:

old names may still appear
very early install flows may predate the current onboarding-centered setup
some discussions capture the growth shock better than the current operating model
later docs are usually better for exact commands, while older sources are still useful for context

That is the right split: use older sources for narrative, and current docs for operation.

The practical takeaway

OpenClaw is not “just another AI project.” Its current ecosystem, security pressure, and comparison landscape all come from a period of extreme growth. If you ignore that context, the rest of the guide becomes harder to interpret.