← NEWS DESK
analysis

The Verified History of OpenClaw: Warelay to OpenClaw

The source-grounded OpenClaw naming timeline: Warelay, Clawd, Clawdis, Clawdbot, Moltbot and OpenClaw, verified against official posts and Git history.

Independent reporting and tested guidance for OpenClaw operators · Editorial standards

Verified timeline of OpenClaw names from Warelay to OpenClaw
Verified timeline of OpenClaw names from Warelay to OpenClaw

The official Jan. 29, 2026 announcement tells the short version: Clawd → Moltbot → OpenClaw. The full repository history is a little messier and a lot more interesting. Before the final name settled, the project also passed through Warelay, Clawdis, and Clawdbot.

That matters because a lot of the old “history” floating around online compresses the sequence, skips intermediate names, or treats launch-day lore as if it were the whole record. The timeline below is checked against the project’s own blog, docs, and Git history.

Verified naming timeline

Date Verified primary source What changed
Nov. 24, 2025 Git history The repo opened with an Initial commit, then the next commit that same day was Add warelay CLI with Twilio webhook support. Warelay is the first real project name in the history.
Nov. 25, 2025 Git history claude: prefix prompt with Clawd identity marks the switch to Clawd.
Dec. 3, 2025 Git history 🦞 Rebrand to CLAWDIS - add docs, update README makes Clawdis the next formal name.
Jan. 4, 2026 Git history chore: rename project to clawdbot moves the project to Clawdbot.
Jan. 27, 2026 Git history refactor: rename clawdbot to moltbot with legacy compat lands the Moltbot rename.
Jan. 29, 2026 Official announcement Peter Steinberger publishes Introducing OpenClaw and announces the new name publicly.
Jan. 30, 2026 Git history refactor: rename to openclaw is the first commit that lands OpenClaw in the repo.

What the official announcement said

Peter’s Jan. 29 post is still the best public summary of the final transition. It says the project came from Clawd and Moltbot, and that the new name is OpenClaw. It also says the project had already crossed 100,000 GitHub stars and pulled 2 million visitors in a single week.

That star claim was true in the announcement’s moment, but it should be read as a dated launch metric, not a permanent property of the project. The current repository star count is much higher now, which is why time-bounding the number matters.

What the repo history adds

The Git history fills in the gaps the announcement skips:

  • Warelay is the earliest project name verified in the repository history.
  • Clawd appears the next day in prompt and identity-related commits.
  • Clawdis is not just lore; it shows up in a formal rebrand commit on Dec. 3.
  • Clawdbot was the January 2026 bridge name before Moltbot.
  • Moltbot appears on Jan. 27, and the repo’s first OpenClaw commit lands Jan. 30.

So the cleaned-up history is not just “Clawd → Moltbot → OpenClaw.” It is:

Warelay → Clawd → Clawdis → Clawdbot → Moltbot → OpenClaw

Common timeline mistakes

Several recurring claims about the naming history need tightening:

  • “The first commit already carried Warelay” — not quite. The repo opened with an Initial commit; the Warelay name appears in the next commit.
  • “Clawdbot lasted over a month” — the Git history I checked shows Clawdbot starting on Jan. 4 and being replaced by Moltbot on Jan. 27.
  • “100K stars” as a timeless fact — it is better framed as the number Peter cited in the Jan. 29 announcement.
  • Any X/Twitter shoutout or anecdote without a primary URL — treat it as unverified unless the original post can be cited directly.

Bottom line

The final name landed quickly, but the path to it was iterative:

  1. a weekend WhatsApp relay,
  2. Warelay,
  3. Clawd,
  4. Clawdis,
  5. Clawdbot,
  6. Moltbot,
  7. and finally OpenClaw.

If you want the shortest accurate version, use the official post. If you want the full verified timeline, use the repo history too.

THE RECEIPTS

Claims should survive the click.

Primary links used for this article are listed openly. If the evidence changes, the verification date changes with it.
  1. 01Introducing OpenClaw
  2. 02OpenClaw lore
  3. 03OpenClaw GitHub repository

THE OPERATOR BRIEF

One useful email when the signal earns it.

Release impact, security changes and repository intelligence. No daily sludge.