From Clawdbot to OpenClaw: Everything You Need to Know
On January 27, 2026, the project formerly known as Clawdbot was officially rebranded to OpenClaw. Here's what happened, what changed, and how to migrate.
Why the Rebrand?
Anthropic, the company behind the Claude AI model, issued a trademark request to project creator Peter Steinberger. The name "Clawdbot" (and the agent name "Clawd") was considered too similar to "Claude", Anthropic's flagship AI product.
The new name "OpenClaw" combines 'Open' (for open source) with 'Claw' (from the project's lobster mascot), representing an AI that can grab and handle real-world tasks with precision. The agent is now named "Claw" instead of "Clawd".
What Changed?
| Before (Clawdbot) | After (OpenClaw) |
|---|---|
| Clawdbot | OpenClaw |
| Clawd | Claw |
| clawdbot | openclaw |
| ~/.clawdbot/ | ~/.openclaw/ |
| npm install -g clawdbot | npm install -g openclaw |
How to Migrate
Migration is straightforward. The clawdbot command still works as a compatibility shim, and legacy config paths are auto-migrated on first run.
# Update to the latest version
npm install -g openclaw@latest
# Your existing config will be auto-migrated
# The old 'clawdbot' command still works as an alias
openclaw --versionYour existing configuration, conversation history, memory, and vault are all preserved during migration. No data is lost.
Migration FAQ
Will I lose my conversation history or memory?
No. All data is preserved. The migration only updates paths and package names. Your conversation history, persistent memory, and vault contents remain intact.
Do I need to update my config files?
No. Legacy config keys (like ~/.clawdbot/) are automatically detected and migrated on first run. You can optionally update them manually, but it's not required.
Does the old 'clawdbot' command still work?
Yes. The clawdbot command is installed as a compatibility shim that redirects to openclaw. It will continue to work, but we recommend switching to the openclaw command.
Are there any breaking changes?
The v2026.1.12 release renamed chat 'providers' to 'channels' across CLI/RPC/config. Legacy config keys auto-migrate, but scripts referencing old API endpoints may need updating.