Claw Sync

**Judgement:** Claw Sync is a focused, generally well-designed backup and restore utility for OpenClaw agents. It’s most appropriate for users who actively manage their agent’s memory/persona and want versioned, Git-based backups. **What it does well** - Provides simple commands for core operations: `/sync`, `/restore`, `/sync-status`, `/sync-list`. - Automatically versions backups (e.g., `backup-YYYYMMDD-HHMM`) so you can restore specific historical states. - Protects some sensitive data by *not* syncing `openclaw.json`, `.env`, and similar secret-bearing config files. - Performs a local backup before restoring, which is a strong safety feature for disaster recovery. - Explicit OpenClaw awareness (standard memory and workspace files) makes it useful out of the box for typical setups. **Key risks & limitations** - **Data exposure risk:** Backups go to a remote repository (e.g., GitHub) using `BACKUP_REPO` and `BACKUP_TOKEN`. If the repo is public, misconfigured, or the token is compromised, your agent’s memory, persona, and custom skills could leak. This is the main risk and must be managed by using private repos and secure token handling. - **No built-in encryption mentioned:** Security relies on repository access controls, not end-to-end encryption of the data itself. - **Restore dangers:** `/restore` (especially with `--force`) can overwrite current memory and workspace files. While a local pre-restore backup mitigates this, users still need to understand the implications before restoring. - **Setup complexity for non-technical users:** Creating a private repo, generating a GitHub token, and configuring `~/.openclaw/.backup.env` may be non-trivial for less technical users. **Recommended scenarios** - You run an OpenClaw agent long-term and care about **reliable, versioned backups** of its memory, persona, and skills. - You frequently experiment with **persona, tools, or skills** and need an easy way to revert to prior states. - You use OpenClaw across multiple devices and want to **synchronize** the agent’s state via a private Git repository. **Caution advised when** - Handling highly sensitive or regulated data in memory/persona (consider additional encryption or stricter storage policies). - Sharing access to the backup repository with others (they will see the agent’s memory and workspace contents).