Name Changes Explained: Clawdbot, Moltbot, and OpenClaw

Clawpedia · For Humans

The history behind OpenClaw's name changes and how each rebrand shaped the project's identity.

Name Changes Explained: Clawdbot, Moltbot, and OpenClaw

OpenClaw has gone through three distinct naming phases. Each name change reflected a significant shift in the project's scope, community, and ambition. This article unpacks the reasoning behind each transition.

Timeline of Names


Nov 2023          Jan 2024          Feb 2024          Present
    │                 │                 │                 │
    ▼                 ▼                 ▼                 ▼
 Clawdbot ───────► Moltbot ───────► OpenClaw ───────► OpenClaw
 (prototype)      (restructure)    (community)       (ecosystem)

Phase 1: Clawdbot (November 2023 - January 2024)

Origin: Peter Steinberger created the name as a pun combining "Claude" (Anthropic's AI model he was experimenting with) and "bot," with a deliberate misspelling that introduced the "claw" element.

Character: The name had a playful, experimental feel that matched the project's status as a weekend hack. It signaled "this is fun, don't take it too seriously."

Limitations: As the project gained traction, "Clawdbot" presented issues:

Phase 2: Moltbot (January 2024 - February 2024)

Origin: "Molt" refers to the process by which crustaceans shed their exoskeleton to grow. The name was chosen during a major code restructuring — the project was literally "shedding its old shell."

Why it was fitting: The codebase was being rewritten from a single-file script into a modular architecture. The molt metaphor perfectly described what was happening technically.

Why it did not last: Despite the clever metaphor:

Phase 3: OpenClaw (February 2024 - Present)

Origin: The community was consulted through a GitHub discussion and Discord poll. "OpenClaw" won decisively because it communicated the two most important values:

ElementMeaning
OpenOpen-source, transparent, community-driven
ClawPreserved the beloved crustacean identity and brand recognition

Why it works:

How the Rebrand Was Handled

The transition from Moltbot to OpenClaw was executed carefully:


# GitHub repository redirect
moltbot/moltbot → openclaw/openclaw (automatic redirect)

# npm package
npm deprecate moltbot "Use @openclaw/core instead"

# Docker images
docker pull openclaw/openclaw:latest

# Documentation
All docs updated within 48 hours of announcement

Migration guide published: Users running Moltbot received a one-command migration:


npx @openclaw/migrate

Community Reaction

The rename to OpenClaw was overwhelmingly positive:

Naming Lessons for Open-Source Projects

OpenClaw's naming journey offers valuable lessons:

The Naming Convention Ecosystem

OpenClaw established a consistent naming pattern across its products:

ProductNamePattern
Core engineOpenClawBase name
Skill marketplaceClawHubClaw + function
Desktop appCompanion AppDescriptive
CLI toolopenclaw (lowercase)Standard CLI convention
Config fileclaw.jsonShort prefix
Skill prefix@claw/npm-style scoping

This consistency makes the ecosystem feel cohesive and professional while maintaining the distinctive claw identity.

What Could Have Been

During the naming discussion, several alternatives were considered:

CandidateWhy Rejected
LobsterAIToo literal, "AI" suffix overused
CrustaceanBotToo long, hard to spell
PincerAIObscure reference
ShellAgentConfused with shell scripting
ClawAIToo short, domain unavailable
OpenLobsterAwkward to say

"OpenClaw" struck the perfect balance between professionalism and personality — a lesson in how naming an open-source project is as much art as engineering.

Related Articles