claw-roam

What This Skill Does

Claw Roam is a specialized synchronization tool designed for OpenClaw users who operate across multiple environments, such as a local workstation and a remote VPS. By leveraging Git as the backbone for state management, it ensures that your OpenClaw workspace—including personality settings, learned memories, and installed skills—remains consistent regardless of where you are working. Instead of manually copying files or losing track of progress, claw-roam automates the version control process, allowing for a seamless transition between machines. The skill simplifies complex branching strategies into intuitive commands, ensuring your AI agent evolves coherently across your entire infrastructure.

Installation

To integrate this capability into your environment, use the OpenClaw skill manager. Ensure your workspace is initialized as a Git repository before usage.

1. Install via CLI: clawhub install openclaw/skills/skills/reed1898/claw-roam
2. Navigate to your workspace directory: cd ~/.openclaw/workspace
3. Initialize your repository: git init
4. Connect to your remote origin: git remote add origin <your-repo-url>

Use Cases

• Seamless Migration: Moving your primary AI environment from a local MacBook to a cloud-based VPS without manual setup.
• Multi-Device Parity: Maintaining a unified memory bank where the agent remembers interactions from both your office desktop and your home server.
• Disaster Recovery: Providing a live, cloud-synced backup of your agent's personality files, ensuring no progress is lost in the event of hardware failure.
• Remote Deployment: Syncing configuration updates or new skills to your agent running in a headless server environment.

Example Prompts

1. "Sync my current workspace to the remote server so I can pick up where I left off on my VPS."
2. "claw-roam status - tell me if there are any pending changes that haven't been pushed to the main repository yet."
3. "I'm shutting down for the day, please run a full sync to make sure my latest memory updates are saved to the cloud."

Tips & Limitations

• Branching: Stick to the recommended workflow (main for shared state, individual branches for specific devices) to avoid complex merge conflicts.
• Frequency: Make it a habit to run claw-roam sync at the end of every session to ensure your remote state matches your local progress.
• Git Dependency: This skill requires a working knowledge of Git remote configurations. Ensure your SSH keys are set up on all machines for the remote repository to avoid authentication prompts. Note that large binary files in your workspace may slow down sync times, so keep your workspace clean of unnecessary logs or large datasets.