openclaw-sync

What This Skill Does

The openclaw-sync skill provides a lightweight, robust, and highly efficient solution for backing up your OpenClaw workspace data. By leveraging the power of rclone and native system cron jobs, this skill enables automated, incremental synchronization across over 70 different cloud storage providers, including S3-compatible services like AWS, Alibaba Cloud OSS, Tencent Cloud COS, and Qiniu, as well as mainstream consumer platforms like Google Drive, OneDrive, and Dropbox. Because it operates via scheduled system tasks rather than maintaining resource-heavy background daemons, it ensures that your system performance remains unaffected while guaranteeing your vital AI memory, agent configurations, and project files are safely persisted in the cloud.

Installation

To install this skill, run clawhub install openclaw/skills/skills/aohoyo/openclaw-sync in your terminal. Ensure that rclone is installed on your host machine; if it is not, execute curl https://rclone.org/install.sh | sudo bash. Once the skill is installed, navigate to the skills/openclaw-sync directory, run rclone config to authenticate with your preferred cloud provider, and edit the config/sync-config.json file to match your desired bucket and interval settings. Finally, run bash scripts/setup-cron.sh to initialize the automated background sync service.

Use Cases

This skill is perfect for developers and AI power users who want to prevent data loss without sacrificing system resources. It is ideal for backing up evolving AI personality files, memory logs, and project-specific tools across multiple machines. It also serves as a professional-grade migration tool for moving your workspace environments between different servers or cloud instances with minimal downtime or manual file transfer efforts.

Example Prompts

1. "OpenClaw, please trigger a manual sync of my workspace right now to ensure the latest changes are backed up."
2. "What is the current status of my cloud backup and when was the last successful sync completed?"
3. "Update my sync configuration to exclude all temporary log files and only upload the core memory modules."

Tips & Limitations

To optimize performance, utilize the sync-list.txt file to explicitly define what should be backed up; excluding bulky folders like node_modules or large build artifacts will significantly speed up sync cycles and reduce cloud storage egress costs. Note that this skill requires direct filesystem access and system-level cron permissions to function. Always verify your cloud provider connection using rclone ls remote_name: before enabling the automated cron job to ensure valid authentication.