openclaw-backup-restore
Backup and restore OpenClaw configuration, agents, sessions, and workspace to/from a private Git repository. Use when the user wants to manually trigger a backup, migrate to a new machine, or restore from a previous state.
Why use this skill?
Securely backup and restore your OpenClaw agents, configuration, and workspace data to a private Git repository. Manage your data lifecycle with ease.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/darinrowe/openclaw-backup-restoreWhat This Skill Does
The openclaw-backup-restore skill acts as an essential disaster recovery and synchronization tool for your OpenClaw environment. It automates the complex process of mirroring your configuration, agents, workspace memory, and session data to a private Git repository. By utilizing a side-by-side directory strategy, the skill ensures that your primary production runtime remains clean and performant while maintaining a full history of your settings. It handles the rsync logic, file exclusions, and git commit orchestration necessary to keep your backup repository updated without manual overhead.
Installation
To begin, ensure you have the OpenClaw CLI installed on your local machine. Use the standard skill installation command: clawhub install openclaw/skills/skills/darinrowe/openclaw-backup-restore. Once installed, you must configure your private repository URL by executing: openclaw config set skills.entries.openclaw-backup-restore.env.OPENCLAW_BACKUP_REPO "[email protected]:your-username/your-repo.git". Finally, ensure that your system has SSH access to your Git provider, as the automated push/pull scripts rely on SSH authentication to perform background synchronization securely.
Use Cases
- Cross-Machine Migration: Effortlessly move your entire OpenClaw setup, including active agents and configurations, from a desktop workstation to a laptop or cloud server.
- Disaster Recovery: Protect your valuable data against hardware failure or accidental deletion by maintaining an off-site remote backup.
- Version Control for Agents: Maintain a history of your agent definitions and workspace files, allowing you to roll back to a known working state if a new integration or configuration causes issues.
- Environment Standardization: Keep multiple OpenClaw instances in sync across different machines.
Example Prompts
- "Backup my current OpenClaw configuration and agents to my private repository."
- "Sync my OpenClaw data to GitHub so I can access it from my other laptop."
- "Restore my environment from the backup repository; I just set up a new machine."
Tips & Limitations
- Security First: Since your data is pushed to a remote repository, ensure the repository is set to 'Private' on your Git provider to protect sensitive workspace data.
- Large Files: The
.gitignoreincluded in the skill automatically skips logs andnode_modules. If you have large custom data files in your workspace, be aware that these may bloat the repository if not managed correctly. - Gateway Restart: Always remember to run
openclaw gateway restartafter a restore operation to ensure the new configuration is loaded correctly by the system daemon.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-darinrowe-openclaw-backup-restore": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, network-access, code-execution
Related Skills
obsidian-official-cli-headless
Install and adapt the official Obsidian CLI for headless Linux servers by using a non-root user, Xvfb virtual display, ACL-based vault access, and an obs wrapper command. Use when the user wants the official Obsidian CLI (not notesmd-cli) on a Debian/Ubuntu-like machine without a normal desktop session, or when root/GUI/display constraints break native CLI use.
multi-agent-filesystem-governance
Govern filesystem organization and file-operation decisions in multi-agent environments. Use when deciding where files should live across agent-private workspaces, shared resources, archives, downloads, scripts, notes, knowledge vaults, and code project folders; when defining directory conventions; when triaging downloads; when preventing cross-agent overwrites; or when standardizing file placement and lifecycle rules for reusable agent setups.
git-backed-obsidian-cli-workflows
Use the official Obsidian CLI for note workflows in a Git-backed vault, including search, read, links/backlinks-style queries, daily-note operations, and lightweight note writes that auto-sync after successful write operations. Use when the official Obsidian CLI is already installed and usable on any supported environment, and the task is about querying or updating notes in an Obsidian vault with Git-backed backup behavior.
git-workflows-pro
Handle advanced git workflows and recovery tasks. Use when the user needs help with interactive rebase, commit cleanup, conflict resolution, reflog recovery, cherry-pick, stash, worktree, bisect, submodule vs subtree decisions, sparse checkout, branch archaeology, or undoing dangerous history mistakes in real repositories.
github-private-repo-ssh-routing
Diagnose and manage SSH keys, host aliases, and Git remotes for GitHub private repositories in multi-repo environments. Use when deploy keys collide, a machine manages multiple private repos, automation or backup scripts push to GitHub, or errors like "Permission denied (publickey)" / "Repository not found" appear despite the repo existing.