ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

Openclaw Self Clone Everything

Skill by crazypeace

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/crazypeace/openclaw-self-clone-everything
Or

name: openclaw-self-clone-everything description: Clone and deploy OpenClaw to a new VPS. Use when you need to install OpenClaw on a fresh remote server via SSH. Steps: (1) Verify SSH access (IP, user, password/key), (2) Install OpenClaw via official non-interactive script, (3) Copy ~/.openclaw data, (4) Prompt to update credentials (e.g., Telegram bot token).

OpenClaw Clone to New VPS

Overview: Deploy OpenClaw to a new VPS using SSH and a non-interactive installer, then copy your ~/.opencl workspace and verify/update credentials.

Prerequisites

  • SSH access to the new VPS: IP address, username, and password (or SSH key)

  • The new VPS runs a supported Linux distribution (verify with the official docs)

  • Ensure outbound connectivity on the new VPS (to fetch the installer)

  • Security: When prompted for passwords, avoid hardcoding them; prefer password prompts or SSH key-based auth.

Procedure

Step 1: Verify SSH connectivity

  • Test access from the current environment to the new VPS.
  • Example (interactive login test):
    ssh USER@VPS_IP
    
  • Replace USER with the provided username and VPS_IP with the target IP.
  • Exit the test SSH session once verified.

If auth uses an SSH key, ensure the private key is available and permissions are tightened (e.g., 600).

Step 2: Install OpenClaw via non-interactive script

  • Run the official installer in non-interactive mode on the new VPS:
    ssh USER@VPS_IP 'bash -c "$(curl -fsSL https://openclaw.ai/install.sh)" -- --no-onboard'
    
  • Explanation:
    • --no-onboard skips the interactive onboarding wizard.
    • This command performs the installation over SSH without prompting.

If the new VPS blocks curl or https://openclaw.ai, download the installer locally and scp/transfer it before running bash install.sh -- --no-onboard.

Step 3: Copy ~/.openclaw from the source to the new VPS

  • Source path (current environment): ~/.openclaw

  • Target directory on the new VPS: ~/.openclaw

  • Create a compressed archive, transfer it, and extract on the new VPS:

    # Compress (on source)
    cd ~ && tar czf openclaw-data.tar.gz --exclude='*.log' --exclude='cache' --exclude='node_modules/.cache' .openclaw
    
    # Transfer
    scp openclaw-data.tar.gz USER@VPS_IP:~/
    
    # Extract (on new VPS)
    ssh USER@VPS_IP 'rm -rf ~/.openclaw && tar xzf ~/openclaw-data.tar.gz -C ~/'
    
    # Cleanup (optional, on both sides)
    rm openclaw-data.tar.gz
    ssh USER@VPS_IP 'rm ~/openclaw-data.tar.gz'
    

Notes and cautions:

  • Review the contents you intend to copy. Avoid copying local temporary files or caches that should not be restored on the target.
  • The example excludes *.log, cache, and node_modules/.cache to reduce archive size; adjust based on your directory layout.
  • No ongoing synchronization; this is a one-time transfer.

Step 4: Update or validate key credentials on the new VPS (Optional)

Metadata

Stars3409
Views0
Updated2026-03-25
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-crazypeace-openclaw-self-clone-everything": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.