Important: If you're seeing this, you likely knew us as "Clawdbot." We've rebranded to Moltbot due to trademark considerations. This guide explains everything you need to know about the transition.

Why the Rebrand?

After careful consideration, we made the decision to rebrand from Clawdbot to Moltbot. This change ensures we can continue developing and distributing this open-source AI assistant without legal complications.

What this means for you:

Same codebase, same features, same team
Better long-term sustainability for the project
No breaking changes to core functionality
Your existing configurations and skills will continue to work

⚠️ Critical Security Warning: Crypto Scams on X/Twitter

WARNING: There are currently cryptocurrency scams impersonating Moltbot on X (formerly Twitter). These accounts claim to offer "Moltbot tokens" or "MOLT crypto" – these are fake and have no affiliation with our project.

Official sources ONLY:

✅ Official GitHub: github.com/moltbot/moltbot
✅ Official Website: https://molt.bot/
✅ Official Discord: https://discord.com/invite/clawd

Red flags to watch for:

❌ Any account promising "airdrops" or "tokens"
❌ Accounts asking for crypto payments or wallet connections
❌ URLs that don't match our official GitHub domain
❌ Accounts not verified in our official Discord server

We will NEVER:

Ask for cryptocurrency or payments
Launch a token or coin
Request your wallet credentials
DM you first about investment opportunities

Stay safe. If it's not in our official GitHub repository, it's not us.

How to Update Your Installation

If you have an existing Clawdbot installation, follow these steps to migrate to Moltbot.

macOS (Homebrew)

Old command (Clawdbot):

brew install clawbot

New command (Moltbot):

brew install moltbot
brew upgrade moltbot

Migration steps:

# 1. Uninstall the old Clawdbot
brew uninstall clawbot

# 2. Install Moltbot
brew install moltbot

# 3. Verify installation
moltbot --version
# Expected output: moltbot v2.x.x

# 4. Your existing config should auto-migrate
moltbot doctor

Linux (APT)

# Remove old Clawdbot repository
sudo rm /etc/apt/sources.list.d/clawbot.list

# Add new Moltbot repository
curl -fsSL https://packages.moltbot.ai/apt/gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/moltbot.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/moltbot.gpg] https://packages.moltbot.ai/apt stable main" | sudo tee /etc/apt/sources.list.d/moltbot.list

# Update and install
sudo apt update
sudo apt install moltbot

Windows (WSL2)

If you're using Windows with WSL2, follow the Linux instructions above within your WSL2 instance.

Your existing ~/.clawbot/ configuration directory will be automatically detected and migrated to ~/.moltbot/ on first run.

Need help with WSL2 setup? Check out our Windows WSL2 Installation Guide for detailed instructions.

Python pip

# Uninstall old package
pip uninstall clawbot

# Install new package
pip install moltbot

# Verify
moltbot --version

Docker

# Old image (deprecated)
FROM clawbot/clawbot:latest

# New image (use this instead)
FROM moltbot/moltbot:latest

Update your Docker Compose files:

services:
  moltbot:
    image: moltbot/moltbot:latest
    container_name: moltbot
    volumes:
      - ./moltbot-config:/root/.moltbot
    ports:
      - "8080:8080"

What's Staying the Same

Good news: almost everything you love about Clawdbot remains unchanged in Moltbot.

Feature Parity

All your favorite features work exactly the same:

✅ Browser automation and control
✅ System monitoring and health checks
✅ Discord integration
✅ Calendar and scheduling
✅ Voice assistant capabilities
✅ Smart home automation
✅ Gateway device pairing
✅ Custom skill development

Configuration Compatibility

Your existing configuration files will be automatically migrated:

# Old location
~/.clawbot/

# New location (auto-migrated on first run)
~/.moltbot/

Migration happens automatically when you first run moltbot start. You don't need to manually copy anything.

Skills and Plugins

All existing skills remain compatible:

Your custom skills in ~/.moltbot/skills/ will continue to work
Community skills from the original Clawdbot ecosystem are forward-compatible
No code changes required for skill developers

Mac Mini M4 Performance: Still Perfect

Great news for Mac Mini M4 users: The Moltbot optimization guide works identically to the Clawdbot setup. If you followed our previous optimization guide, you're already set.

The architecture hasn't changed – Moltbot still benefits from:

✅ M4's unified memory architecture for efficient AI processing
✅ Low-power background execution (24/7 availability)
✅ Hardware-accelerated video encoding for browser automation
✅ Thermal efficiency for continuous operation

Update Your M4 Mac Mini Setup

If you have an existing M4 Mac Mini running Clawdbot:

# 1. Stop the old service
sudo launchctl unload /Library/LaunchDaemons/com.clawbot.daemon.plist

# 2. Install Moltbot
brew install moltbot

# 3. Update the launch daemon plist
sudo nano /Library/LaunchDaemons/com.moltbot.daemon.plist

Updated plist content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.moltbot.daemon</string>
    <key>ProgramArguments</key>
    <array>
        <string>/opt/homebrew/bin/moltbot</string>
        <string>daemon</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
    <key>StandardOutPath</key>
    <string>/var/log/moltbot.log</string>
    <key>StandardErrorPath</key>
    <string>/var/log/moltbot.err</string>
</dict>
</plist>

# 4. Load the new service
sudo launchctl load /Library/LaunchDaemons/com.moltbot.daemon.plist

# 5. Verify it's running
moltbot status

For the complete Mac Mini M4 optimization guide, including energy saver settings, network configuration, and performance tuning, see our Best-in-class Mac Mini M4 Setup Guide. This is the definitive resource for getting maximum performance from Moltbot on Apple Silicon.

CLI Command Reference

Here's a quick reference for common commands. Note that all commands now use moltbot instead of clawbot:

Old Command (Clawdbot)	New Command (Moltbot)	Description
`clawbot start`	`moltbot start`	Start the Moltbot daemon
`clawbot stop`	`moltbot stop`	Stop the daemon
`clawbot status`	`moltbot status`	Check running status
`clawbot doctor`	`moltbot doctor`	Run diagnostics
`clawbot logs`	`moltbot logs`	View daemon logs
`clawbot pair`	`moltbot pair`	Pair a new gateway device
`clawbot skills list`	`moltbot skills list`	List installed skills
`clawbot skills install <name>`	`moltbot skills install <name>`	Install a skill
`clawbot config get <key>`	`moltbot config get <key>`	Get config value
`clawbot config set <key> <val>`	`moltbot config set <key> <val>`	Set config value

Breaking Changes

We've minimized breaking changes, but here are a few things to be aware of:

1. CLI Command Name Change

All CLI commands now use moltbot instead of clawbot. Update your scripts, aliases, and documentation.

Check your shell aliases:

# In ~/.zshrc or ~/.bashrc, remove or update:
alias clawbot='moltbot'  # Optional: add this for a transition period

2. Systemd/Launchd Service Names

If you're running Moltbot as a system service, update the service file names:

macOS (launchd):

Old: com.clawbot.daemon.plist
New: com.moltbot.daemon.plist

Linux (systemd):

Old: clawbot.service
New: moltbot.service

3. Environment Variables

If you're using environment variables in your configuration:

# Old
CLAWBOT_HOME=/path/to/config
CLAWBOT_LOG_LEVEL=debug

# New
MOLTBOT_HOME=/path/to/config
MOLTBOT_LOG_LEVEL=debug

The old CLAWBOT_* variables are deprecated but still supported for now. We recommend updating to MOLTBOT_* prefixes.

4. Package Repository URLs

If you've pinned our package repositories in your configuration, update the URLs:

Homebrew: brew tap moltbot/moltbot
APT: packages.moltbot.ai/apt
Docker Hub: moltbot/moltbot

GitHub Repository Migration

The main development repository has moved:

Old: github.com/clawbot/clawbot (archived, read-only)
New: github.com/moltbot/moltbot (active development)

What you need to do:

If you have forked or starred the old repository, please update to the new one:

# If you have a local clone
cd clawbot
git remote set-url origin https://github.com/moltbot/moltbot.git
git fetch origin
git checkout main
git pull origin main

If you're submitting pull requests or reporting issues, use the new repository at github.com/moltbot/moltbot.

Documentation Updates

Our documentation is being updated to reflect the Moltbot branding. Here are the key pages you should reference:

Essential Setup Guides

Mac Mini M4 Setup Guide – Best-in-class guide for Moltbot users, covering macOS 15 optimization, energy efficiency, and 24/7 background execution
Windows WSL2 Installation – Complete Windows setup with USB/Serial passthrough
Gateway Troubleshooting – Fix pairing failures and connection issues
Device Pairing – Interactive pairing interface for gateways

Skill Documentation

All skill documentation remains relevant and has been updated to use Moltbot CLI examples:

Migration Checklist

Use this checklist to ensure you've fully migrated to Moltbot:

Frequently Asked Questions

Q: Do I need to reinstall my skills? A: No. Your installed skills in ~/.moltbot/skills/ will continue to work without modification.

Q: Will my Clawdbot gateway devices still work? A: Yes. Gateway devices are compatible with Moltbot. No re-pairing required.

Q: What happens to my logs and data? A: Your data is automatically migrated to ~/.moltbot/ on first run. The old ~/.clawbot/ directory is preserved as a backup.

Q: Is Clawdbot still safe to use? A: Clawdbot will receive security updates for a limited time, but we strongly recommend migrating to Moltbot as soon as possible. New features will only be developed for Moltbot.

Q: What if I find a Clawdbot reference in the docs? A: We're in the process of updating all documentation. If you spot outdated references, please open an issue to help us improve.

Q: Can I run Clawdbot and Moltbot side-by-side? A: We don't recommend this. They use the same ports and resources. Please fully migrate to Moltbot.

Q: Will there be another rebrand? A: No. We've secured the Moltbot trademark and this name is permanent.

What's Next for Moltbot?

The rebrand clears the way for exciting new features we've been planning:

Enhanced Gateway V2 – Next-generation hardware with improved latency
Web Dashboard – Browser-based management interface
Multi-language Support – Better internationalization
Plugin Marketplace – Discover and install community skills
Cloud Sync – Sync configurations across devices (optional, opt-in only)

Follow our progress on GitHub and join our Discord community for early access announcements.

Need Help?

If you encounter issues during migration:

Check the troubleshooting guide – Gateway Troubleshooting
Run diagnostics – moltbot doctor will identify common issues
Search existing issues – GitHub Issues
Join our Discord – Get real-time help from the community (link in GitHub README)
Open a new issue – Include moltbot doctor output and your OS/version

Summary

What Changed	Status
Project name	Clawdbot → Moltbot
CLI command	`clawbot` → `moltbot`
Config directory	`~/.clawbot/` → `~/.moltbot/` (auto-migrated)
GitHub repository	`clawbot/clawbot` → `moltbot/moltbot`
Package name	`clawbot` → `moltbot`
Core functionality	✅ Unchanged
Skills compatibility	✅ Fully compatible
Hardware support	✅ Including Mac Mini M4
Your data	✅ Auto-migrated

Thank you for your patience during this transition. We're excited to continue building the best open-source AI assistant under our new name: Moltbot.

Last updated: January 28, 2025

Clawdbot is now Moltbot: What Changed and How to Update