ClawVault
by @getlighty
Portable identity vault for OpenClaw. Syncs knowledge, packages, and memory across machines like iCloud — automatic, invisible, encrypted. Bring your own sto...
clawhub install getlighty-clawvault📖 About This Skill
name: clawvault description: > Portable identity vault for OpenClaw. Syncs knowledge, packages, and memory across machines like iCloud — automatic, invisible, encrypted. Bring your own storage (Google Drive, Dropbox, FTP, Git) or use ClawVault Cloud. version: 2.0.0 author: clawvault license: MIT tags: - sync - identity - migration - packages - backup - roaming triggers: - vault - sync - migrate - packages - roam - backup - restore - cloud tools: - exec - file
ClawVault — Portable Agent Environment
You are an OpenClaw agent with the clawvault skill installed. This skill gives you automatic, continuous sync of the user's knowledge and environment across all their machines — like iCloud for AI agents.
Architecture
ClawVault works like a combination of iCloud and Git:
Providers
| Provider | Type | Setup |
|----------|------|-------|
| ClawVault Cloud | Managed (paid per MB) | One command — clawvault cloud signup |
| Google Drive | BYOS (free) | OAuth flow via clawvault provider gdrive |
| Dropbox | BYOS (free) | OAuth flow via clawvault provider dropbox |
| FTP/SFTP | BYOS (free) | Host + credentials via clawvault provider ftp |
| Git | BYOS (free) | Any git remote via clawvault provider git |
| S3 | BYOS (free) | Any S3-compatible via clawvault provider s3 |
| WebDAV | BYOS (free) | Nextcloud etc via clawvault provider webdav |
| Local | BYOS (free) | USB/NAS mount via clawvault provider local |
"BYOS" = Bring Your Own Storage. Free forever. ClawVault Cloud is the convenience option for people who don't want to manage storage.
What Syncs
ALWAYS SYNCED (shared knowledge pool):
identity/USER.md Who you are
knowledge/MEMORY.md Long-term memory
knowledge/projects/ Project context
requirements.yaml System packages
skills-manifest.yaml Installed skills listNEVER AUTO-SYNCED (per-instance):
local/SOUL.md This agent's personality
local/IDENTITY.md This agent's identity
local/config-override Local config tweaks
OPT-IN SYNC:
openclaw config.json Gateway/model config
credentials/ Channel auth (encrypted separately)
Commands
When the user asks about vault operations, use these:
First-Time Setup
clawvault.sh init — creates vault, generates Ed25519 keypair, scans packages
clawvault.sh cloud signup — creates cloud account, auto-configures provider
clawvault.sh provider gdrive — OAuth flow for Google Drive
clawvault.sh provider dropbox
clawvault.sh provider ftp — asks for host, port, credentialsDaily Use (mostly invisible)
clawvault.sh status — show sync state, last push/pull, provider info
sync-engine.sh push — force immediate sync
sync-engine.sh log — show commit history (like git log)
sync-engine.sh rollback — revert to previous state
sync-engine.sh diff — show pending changesPackages
track-packages.sh scan
track-packages.sh diff
track-packages.sh install — shows commands, asks before runningMigration
migrate.sh pull — interactive restore wizard
migrate.sh push-identity — explicit opt-in onlyProfiles
Each machine backs up to its own named profile (default: hostname). Profiles are separate — different machines can have different knowledge, memory, and packages without interfering with each other.clawvault.sh profile show — displays current profile name
clawvault.sh profile list — lists all profiles in the remote storage
clawvault.sh profile rename — renames this machine's profile
clawvault.sh profile pull — restores a specific profile to this machine
(overwrites local vault with that profile's data, does NOT affect the source)Key Management
keypair.sh show-public — display public key (for adding to providers)
keypair.sh rotate — generates new keypair, re-registers with providerBehavior Rules
1. Auto-sync is ON by default after setup — like iCloud. The user should not have to think about syncing. Changes are pushed within 30 seconds.
2. Never sync SOUL.md or IDENTITY.md without explicit permission.
3. Always confirm before installing packages. Show the diff, let them pick.
4. Private key never leaves the machine. It's stored in
~/.clawvault/keys/ with 600 permissions. The public key is registered
with the vault provider.
5. Conflicts: If remote has changes the user hasn't seen, show a diff and let them choose. Auto-merge for non-conflicting changes (like git).
6. Be transparent about costs. If using ClawVault Cloud, show current usage and estimated cost when asked. Never surprise the user with charges.
7. Offline-first. Everything works locally. Sync happens when connectivity is available. Queue changes and push when back online.
8. Profiles are separate by default. Each machine pushes to its own named
profile (default: hostname). Profiles never merge automatically. If the user
wants data from another machine, they must explicitly pull that profile with
clawvault.sh profile pull .
ClawVault Cloud Pricing
When users ask about pricing: