Cross Device Sync

What This Skill Does

The Cross-Device Sync skill is a powerful utility designed for OpenClaw users who operate across multiple environments. By leveraging GitHub as a centralized, encrypted, or private repository, this skill enables seamless, bi-directional synchronization of your OpenClaw memory files. It automates the complex Git operations—pulling, merging, and pushing—ensuring that your agent retains context, learned behaviors, and stored data regardless of whether you are working on a laptop, desktop, or server. The skill simplifies the maintenance of your agent's digital brain, ensuring consistency across your entire hardware fleet.

Installation

To integrate this capability into your OpenClaw environment, execute the following command in your terminal:

npx clawhub install cross-device-sync

Alternatively, for full repository path installations: clawhub install openclaw/skills/skills/coreyleung-art/cross-device-sync

Ensure you have a Personal Access Token (PAT) from GitHub with repository read/write permissions ready before running the setup script, as the installation wizard will prompt for these credentials to finalize the linkage.

Use Cases

• Multi-Device Workflow: Maintain a consistent persona and knowledge base when switching between a personal laptop and a professional workstation.
• Team Collaboration: Share agent memory files within a private repository to allow team members to access updated agent insights.
• Data Backup: Use the GitHub repository as a version-controlled backup system for your agent's memory, allowing you to roll back to previous states if unexpected changes occur.
• Server-Side Persistence: Synchronize memory to a cloud-based development server to ensure your agent stays active and updated even when your local machine is offline.

Example Prompts

• "OpenClaw, please run the setup process to sync my memory files with my private repository at github.com/user/my-agent-data."
• "Perform an immediate synchronization now to push my latest learned patterns to the cloud repository."
• "What is the current sync status of my agent memory, and are there any pending conflicts that require my attention?"

Tips & Limitations

• Security First: Always use a private GitHub repository for your memory files, as they may contain personal or sensitive data. Never share your Personal Access Token in public scripts or logs.
• Conflict Management: While the skill provides built-in conflict resolution, frequent manual commits from multiple machines simultaneously can sometimes lead to merge conflicts that require manual resolution in the repository dashboard.
• Frequency: You can automate the frequency of synchronization to balance between real-time data persistence and resource utilization. We recommend setting up a periodic sync rather than constant polling to preserve network and compute resources.
• Token Rotation: Treat your GitHub PAT like a password; rotate it every 90 days to maintain optimal security hygiene.