clawsync

What This Skill Does

ClawSync acts as the central nervous system for your OpenClaw agents. By creating a portable identity vault, it synchronizes your agent's knowledge, project memory, and system configurations across all your devices. It functions similarly to iCloud or Git, ensuring that your AI assistant remains consistent, context-aware, and up-to-date regardless of which machine you are currently working from. Whether you are using a cloud-managed service for convenience or your own preferred storage backend (like S3, FTP, or Google Drive), ClawSync maintains a versioned, encrypted, and continuous stream of your agent's digital "brain."

Installation

To integrate ClawSync into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/getlighty/getlighty-clawsync After installation, initialize your vault by running clawsync.sh init. This process establishes your security credentials and prepares the sync engine.

Use Cases

• Multi-Device Parity: Maintain the same project context, learned requirements, and skill manifest whether you are on your workstation, laptop, or server.
• Disaster Recovery: Because every change is a versioned commit, you can easily roll back to a previous state if an experimental agent configuration corrupts your current workflow.
• Privacy-First Sync: Use the "Bring Your Own Storage" (BYOS) feature to keep your sensitive memory logs on infrastructure you control, like a private WebDAV server or local NAS.
• Environment Portability: Quickly bootstrap a new agent instance on a fresh machine by syncing your existing requirements.yaml and knowledge/ directories.

Example Prompts

1. "I'm setting up a new laptop, can you initialize the vault and link my Google Drive?"
2. "Check the current sync status and tell me when the last memory commit happened."
3. "I think I made a mistake in the recent memory update, can you rollback the vault to the previous version?"

Tips & Limitations

• Security: ClawSync uses Ed25519 keypairs. Ensure your private keys are backed up safely; if lost, your encrypted data cannot be recovered.
• Scope: Note that 'SOUL' and 'IDENTITY' files are explicitly excluded from sync to preserve the unique personality of each local instance.
• Connectivity: While most providers support offline caching, an active internet connection is required to push new commits to your remote storage. Regularly check sync-engine.sh log to ensure your local history matches the cloud state.