agent-migrate

What This Skill Does

The agent-migrate skill provides a standardized, robust mechanism for moving OpenClaw agents between different computing environments. It encapsulates the complex task of bundling an agent's identity, long-term memory, configuration, and custom extensions into a portable format. By ensuring all critical state components—including workspace/, .openclaw/, and custom skills/—are preserved, it allows for seamless transitions from local development setups to production server environments or disaster recovery backups.

Installation

To integrate this utility into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/haha8d/agent-migrate Ensure you have the necessary system permissions to execute scripts located in the scripts/ directory after installation.

Use Cases

• Production Deployment: Easily clone a refined local development agent to a high-availability cloud server.
• Disaster Recovery: Automate full state backups so that you can restore your agent's personality and memory if a host system fails.
• Environment Sync: Keep development and production environments synchronized by pushing state updates through version-controlled repositories.
• Agent Versioning: Create snapshots before performing significant configuration changes, allowing for full rollback capabilities.

Example Prompts

1. "Agent, please export my current configuration and memory to an archive named 'production-ready-v1' for deployment."
2. "I've moved the export folder to the new server; please run the restoration script to finish the migration process."
3. "Back up my entire agent state to my GitHub repository so I can pull it onto my laptop later."

Tips & Limitations

When migrating across different operating systems (e.g., from macOS to Linux), always verify file permissions on the target system to ensure executable scripts remain functional. Note that this skill is strictly for OpenClaw components; it should not be used as a general-purpose backup tool for personal files or databases. For database-specific migrations, rely on native engine utilities. Always choose the --replace flag during import if you intend to perform a clean install, or use --merge if you wish to supplement an existing agent's memory with new data. If utilizing GitHub for sync, ensure your repository uses encrypted secrets for sensitive environment configuration data.