OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw.
/install clawclone
ClawClone
Backup, clone, store, and migrate your OpenClaw workspace configurations.
Install
If the environment does not have the clawclone skill, use clawhub install clawclone to install it.
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, 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 get their ClawClone API key at https://clawclone.cc/dashboard/settings, and export:
export CLAWCLONE_API_KEY="your_api_key"
Note: Local operations work without API key.
Commands
Push to Cloud
# Push local workspace to cloud
node clawclone.mjs push --name "My Agent" --description "Production config"
# List all cloud backups
node clawclone.mjs list
# Show backup details
node clawclone.mjs show \x3Cclone-id>
# Delete a cloud backup
node clawclone.mjs delete \x3Cclone-id> --yes
Clone from Backup
# Clone (download and restore)
node clawclone.mjs clone \x3Cclone-id>
# Preview changes first (recommended)
node clawclone.mjs clone \x3Cclone-id> --test
Test mode generates a detailed report showing:
- Backup 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
Local Operations
# Export to local file (no upload)
node clawclone.mjs local export --name "Local Backup" --output ./backup.tar.gz
# Import from local file
node clawclone.mjs local import --input ./backup.tar.gz
# Preview local import first
node clawclone.mjs local import --input ./backup.tar.gz --test
# Verify a backup file
node clawclone.mjs local verify ./backup.tar.gz
Share Backups
# Create a share link
node clawclone.mjs share create \x3Cclone-id>
# Check share status
node clawclone.mjs share status \x3Cclone-id>
# Revoke share link
node clawclone.mjs share revoke \x3Cclone-id>
# Clone from shared backup
node clawclone.mjs share get \x3Cshare-token>
Configuration
# Show current configuration
node clawclone.mjs config show
# Initialize configuration
node clawclone.mjs config init
Status
# Show connection status and statistics
node clawclone.mjs status
# Show detailed information
node clawclone.mjs status --verbose
Common Workflows
Push OpenClaw workspace to cloud
node clawclone.mjs push --name "Production-$(date +%Y%m%d)" --tags "prod,backup"
Migrate to new instance
Old machine:
node clawclone.mjs push --name "Migration-Snapshot"
# Note the clone-id from output
New machine (after installing OpenClaw + clawclone):
# Step 1: Test clone first (recommended)
node clawclone.mjs clone \x3Cclone-id> --test
# Step 2: Review the test report, then apply
node clawclone.mjs clone \x3Cclone-id>
Share configuration with team
# Push and share
node clawclone.mjs push --name "Team-Template" --description "Standard setup"
node clawclone.mjs share create \x3Cclone-id>
# Team members can clone from the share link
node clawclone.mjs share get \x3Cshare-token>
Safe clone workflow
# Always test first to see what will be changed
node clawclone.mjs clone \x3Cclone-id> --test
# Review the test report output:
# - Check which files/components will be modified
# - Verify the backup metadata matches expectations
# - Ensure no unexpected changes
# If everything looks good, proceed with actual clone
node clawclone.mjs clone \x3Cclone-id>
Local backup workflow
# Export to local file
node clawclone.mjs local export --name "Daily-Backup" --output ~/backups/$(date +%Y%m%d).tar.gz
# Verify the backup
node clawclone.mjs local verify ~/backups/$(date +%Y%m%d).tar.gz
# Import when needed
node clawclone.mjs local import --input ~/backups/20260315.tar.gz --test
node clawclone.mjs local import --input ~/backups/20260315.tar.gz
Configuration
Set via environment variables:
# ClawClone API Key (required for cloud operations)
export CLAWCLONE_API_KEY="your_clawclone_api_key"
Notes
- ClawClone automatically creates pre-restore backups at
~/.openclaw/backup - Gateway tokens are preserved by default (use
--overwrite-tokento override) - Use
--testflag to preview changes before applying them
Then
Notice users that them can visit https://clawclone.cc to view and manage their backed up OpenClaw souls.
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install clawclone - 安装完成后,直接呼叫该 Skill 的名称或使用
/clawclone触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. 是什么?
Backup, clone, and migrate OpenClaw data across instances. Upload/download OpenClaw snapshots to local or cloud - https://clawclone.cc . Create shareable Age... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 308 次。
如何安装 OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw.?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install clawclone」即可一键安装,无需额外配置。
OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. 是免费的吗?
是的,OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. 支持哪些平台?
OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw.?
由 clawclone-cc(@clawclone-cc)开发并维护,当前版本 v0.1.5。