Connect instance
Link your OpenClaw instance with a single CLI command. Takes 10 seconds.
Connect once, snapshot instantly, restore anywhere — without rebuilding memory, skills, and config.
Link your OpenClaw instance with a single CLI command. Takes 10 seconds.
Capture workspace state — memory, skills, config — in one atomic snapshot.
Restore to any instance whenever you need it. Your workspace travels with you.
New laptop, cloud instance, or CI runner — bring your full workspace along without manual copy-paste.
Memory banks, custom skills, project config — never reconstruct them by hand again.
No GUI needed. Everything works from your terminal.
npx clawon loginAuthenticate with your API key
npx clawon backupSnapshot your entire workspace
npx clawon restoreRestore from any snapshot
npx clawon listView all your backups
A workspace is like a GitHub repo — it's a container that holds cloud snapshots for one OpenClaw installation. Create multiple workspaces for different machines (e.g., "Personal Laptop", "Work Server", "VPS"). A default workspace is created automatically when you sign up.
Workspace markdown files (memory, notes), skills, canvas data, and agent configs. Basically everything that makes your OpenClaw setup yours. Database files, lock files, sessions, and node_modules are automatically skipped — only the stuff you'd actually want to move to another machine.
By default, Clawon backs up your workspace markdown files — the source of truth for memory. The SQLite search index (memory/main.sqlite) is excluded by default because OpenClaw can rebuild it. However, the reindex process has had reliability issues, so we recommend using --include-memory-db for backups to be safe. Free for local, available on Hobby and Pro for cloud.
Yes. Run clawon local schedule on to set up automatic local backups every 12 hours via cron (macOS/Linux). Cloud scheduled backups are available on Hobby and Pro plans. Use clawon schedule status to check your current schedule.
No. The entire credentials/ directory is excluded by default — API keys, tokens, and auth files never leave your machine. Clawon only captures workspace content like markdown, skills, and config JSON. You can also run clawon files before any backup to see exactly what will be uploaded. Plus, every backup is automatically scanned for leaked API keys, tokens, and private keys using 221 detection rules. Flagged files are skipped by default — or you can review and choose. Need to include sensitive files? Use --encrypt to encrypt your backup with AES-256-GCM before anything leaves your machine.
No. Clawon runs as an external companion tool. No changes to OpenClaw core required.
You can — but you'd need to know which files to grab, which to skip (database locks, sessions, credentials), and deal with path differences between machines. Clawon handles the filtering, versioning, and transfer in one command. It also keeps multiple snapshots so you can roll back if something breaks.
Yes. Use --include-sessions to include your chat history (agents/*/sessions/) in backups. Sessions are excluded by default because they can grow large (~30 MB). Local session backups are free; cloud session backups require a Hobby or Pro account.
Your data is never locked in. Run clawon local backup to save a full snapshot to your own machine — no account, no cloud, no internet required. Local backups are unlimited and free. The cloud is there for convenience (cross-machine sync, versioned history), but you always have a local escape hatch.