← Back to Skills Marketplace
OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw.
by
clawclone-cc
· GitHub ↗
· v0.1.5
· MIT-0
308
Downloads
1
Stars
2
Active Installs
4
Versions
Install in OpenClaw
/install clawclone
Description
Backup, clone, and migrate OpenClaw data across instances. Upload/download OpenClaw snapshots to local or cloud - https://clawclone.cc . Create shareable Age...
README (SKILL.md)
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.
Usage Guidance
This skill appears to do what it says (backup, local export/import, and cloud sync). Before using cloud features or running the bundled JS, review the bundled clawclone.mjs for network calls and hardcoded endpoints (look for fetch/axios/https.request and domains beyond clawclone.cc). Be aware that by default it preserves and may upload API keys and 'gateway tokens' — if you have secrets you do not want uploaded, use local export/verify/import workflows instead. Because the package source/homepage is unknown, prefer running it in an isolated environment first, inspect the code for unexpected domains or telemetry, and rotate any tokens/keys after migrating or sharing backups. If you are unsure, avoid using cloud push/share operations until you've verified the implementation.
Capability Analysis
Type: OpenClaw Skill
Name: clawclone
Version: 0.1.5
The skill is designed to exfiltrate the entire OpenClaw environment, including sensitive memory, configurations, and explicitly 'API keys and tokens,' to an external third-party service (https://clawclone.cc). While framed as a backup and migration utility, the broad permissions (read/write access to ~/.openclaw/ and network access) and the explicit focus on credential collection pose a significant security risk. Additionally, the primary execution logic in clawclone.mjs is missing from the provided files, making it impossible to verify if the data is handled securely or if the tool contains hidden malicious behaviors.
Capability Assessment
Purpose & Capability
Name, description, declared required binaries (node, tar, npm), and declared permissions (read/write ~/.openclaw, network: https) match the behaviors you would expect from a backup/restore and cloud-sync CLI.
Instruction Scope
SKILL.md limits actions to backing up/restoring ~/.openclaw and local files and describes cloud push/list/clone/share operations. It explicitly preserves 'gateway tokens' and other API keys by default, which is functionally consistent with a full-state backup but increases sensitivity — users should expect these secrets may be uploaded when using cloud features. The instructions also refer to an environment variable (CLAWCLONE_API_KEY) even though the registry metadata lists no required env vars.
Install Mechanism
No external install spec (instruction-only) and the package bundles a large clawclone.mjs file (vendorized Node code). There are no downloads from arbitrary URLs in the manifest, which reduces supply-chain risk, but the large embedded JS means you should inspect the file for unexpected network endpoints or telemetry before running.
Credentials
No environment variables are declared as required in registry metadata, but SKILL.md instructs users to set CLAWCLONE_API_KEY for cloud features. Requiring an API key for cloud operations is proportionate, but explicit handling/preservation of other API keys and 'gateway tokens' makes the tool capable of exfiltrating sensitive credentials if used with cloud upload — this is expected for a full backup tool but is security-sensitive.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform presence. It writes backups under ~/.openclaw/backup which is appropriate for its purpose and does not claim to modify other skills or global agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install clawclone - After installation, invoke the skill by name or use
/clawclone - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.5
- Added a "Then" section notifying users they can visit https://clawclone.cc to view and manage their backed up OpenClaw souls.
- No other changes to commands, features, or workflows.
v0.1.3
- Updated documentation for improved clarity and structure.
- New and renamed commands for cloud and local backup operations (e.g., push, clone, local export/import, share).
- Added detailed instructions and workflows for sharing, verifying, and testing backups.
- Added command references for status checks, configuration, and share link management.
- Notes clarify automatic pre-restore backups and token preservation behavior.
v0.1.2
- Documentation updates for clarity and brevity.
- Added the official ClawClone website link (https://clawclone.cc) to cloud snapshot sections.
- Clarified instructions for obtaining the ClawClone API key and setting environment variables.
- Updated installation instructions to mention `clawhub install clawclone` if the skill is missing.
- Minor consistency and formatting improvements throughout the documentation.
v0.1.1
- Initial release of clawclone.
- Backup, clone, and migrate complete OpenClaw data, including memory, skills, agents, and settings.
- Supports uploading and downloading OpenClaw snapshots to/from cloud storage.
- Enables sharing Agent configurations and syncing OpenClaw state across devices.
- Includes test/preview mode to safely review changes before restoring.
- Local operations available without API key; cloud features require CLAWCLONE_API_KEY.
Metadata
Frequently Asked Questions
What is 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... It is an AI Agent Skill for Claude Code / OpenClaw, with 308 downloads so far.
How do I install OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw.?
Run "/install clawclone" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. free?
Yes, OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. support?
OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw.?
It is built and maintained by clawclone-cc (@clawclone-cc); the current version is v0.1.5.
More Skills