---

name: clawclone description: "Backup, clone, and migrate OpenClaw data across instances. Upload/download OpenClaw snapshots to cloud storage. Create shareable Agent configurations, sync between devices, and restore complete OpenClaw state including memory, skills, agents, and settings. Use when user wants to backup their OpenClaw data, share configurations, migrate to new server, or create snapshots." metadata: openclaw: requires: bins: ["node", "tar", "npm"] trust: high permissions: - read: ~/.openclaw/ - write: ~/.openclaw/ - network: https

🔄 OpenClaw Clone

⚡ Install

Just tell your OpenClaw agent:

"Help me install clawclone"

Or manually:

clawhub install clawclone

What Gets Backed Up

Component	Details
🧠 OpenClaw Data	MEMORY.md, skills, agent files, configurations
⚙️ Settings	Agent preferences and custom settings
📦 Files	User data and OpenClaw artifacts
🔧 Config	Optional: API keys and tokens (if configured)

Backup Location: ~/.openclaw/backup

Dependencies

Requires: node (v16+), tar, npm (all standard on OpenClaw instances).

Check: which node tar npm

Prerequisites

Before using cloud features (pack, list, get, delete), verify the environment variable is set:

# Check if CLAWCLONE_API_KEY is set
echo $CLAWCLONE_API_KEY

If empty or not set, ask the user to provide their ClawClone API key, then set it:

export CLAWCLONE_API_KEY="your_api_key"

Note: Local operations (export, import) work without API key.

Usage

Create and upload a clone

node clawclone.mjs pack --name "My AI Assistant" --description "Production ready config"

List all your clones

node clawclone.mjs list

Download and apply a clone

node clawclone.mjs get --clone-id <clone-id>

Test restore (preview changes without applying)

# Test cloud clone restore
node clawclone.mjs get --clone-id <clone-id> --test

# Test local file import
node clawclone.mjs import --input ./backup.tar.gz --test

Test mode generates a detailed report showing:

• Clone metadata (name, version, creation date)
• Components that will be modified (workspace, config, skills, etc.)
• File counts and sizes for each component
• No actual changes are made to your system

Export to local file (no upload)

node clawclone.mjs export --name "Local Backup" --output ./backup.tar.gz

Import from local file

node clawclone.mjs import --input ./backup.tar.gz

Delete a cloud clone

node clawclone.mjs delete --clone-id <clone-id> --confirm

Check status

node clawclone.mjs status

Common Workflows

Backup OpenClaw data to cloud

node clawclone.mjs pack --name "Production-$(date +%Y%m%d)" --tags "prod,backup"

Migrate to new instance

Old machine:

node clawclone.mjs pack --name "Migration-Snapshot"
# Note the clone-id from output

New machine (after installing OpenClaw + clawclone):

# Step 1: Test restore first (recommended)
node clawclone.mjs get --clone-id <clone-id> --test

# Step 2: Review the test report, then apply
node clawclone.mjs get --clone-id <clone-id>

Share configuration with team

node clawclone.mjs pack --name "Team-Template" --description "Standard setup for new members"
# Share the clone-id with your team

Test before restoring (safe workflow)

# Always test first to see what will be changed
node clawclone.mjs get --clone-id <clone-id> --test

# Review the test report output:
# - Check which files/components will be modified
# - Verify the clone metadata matches expectations
# - Ensure no unexpected changes

# If everything looks good, proceed with actual restore
node clawclone.mjs get --clone-id <clone-id>

Configuration

Set via environment variables (create .env file or export):

# ClawClone API Key (required for cloud sync)
export CLAWCLONE_API_KEY="your_clawclone_api_key"

Note: ClawClone automatically backs up and restores OpenClaw data at ~/.openclaw/backup