claw-sync

You can backup OpenClaw memory files and custom skills by running a sync command that pushes your current workspace state to a remote Git repository. This automatically creates versioned backups of user profiles, agent personas, and tool configurations.

Disaster recovery for an OpenClaw workspace involves restoring your entire environment from a remote Git repository. The sync process maintains local backups before each restore operation, ensuring you can safely recover memory files and custom skills.

Secure sync protects sensitive configuration files by excluding them from the synchronization process entirely. It also enforces URL validation and path protection to ensure data integrity when pushing memory files and tool configurations to a remote repository.

Yes, versioned backups allow you to restore any previous state of your OpenClaw workspace. Each sync operation creates a tagged version of your data, enabling point-in-time recovery of memory files, user profiles, and custom skills.

To migrate OpenClaw workspaces to a new machine, you restore your entire environment from the remote Git repository. This pulls down your memory files, agent personas, workspace conventions, daily logs, and custom skills directly.

Synchronizing OpenClaw memory includes memory files, user profiles, agent personas, tool configurations, workspace conventions, daily logs, and custom skills. It securely pushes all these data types to your remote Git repository for versioned backups.