Install locally (preferred over npx for auditing): npm install -g clawon@0.1.11
Or pin the version with npx: npx clawon@0.1.11
For higher assurance, clone the repo and build from source: git clone https://github.com/chelouche9/clawon-cli && cd clawon-cli/packages/cli && npm install && npm run build
What You Can Do
Discover — show which files would be backed up
Local backup — save a .tar.gz snapshot to ~/.clawon/backups/ (no account needed)
Cloud restore — pull workspace from cloud to any machine
Scheduled backups — automatic local or cloud backups via cron
Status — check connection, file count, and schedule info
How to Use
All commands run via npx clawon@0.1.11. Always run discover first so the user can see what will be included.
Discovery (always start here)
npx clawon@0.1.11 discover
npx clawon@0.1.11 discover --include-memory-db # Also show SQLite memory index
npx clawon@0.1.11 discover --include-sessions # Also show chat history
Show the output to the user. Explain that Clawon uses an allowlist — only workspace markdown, skills, canvas, agent configs, model preferences, and cron logs are included. Credentials are always excluded.
Local Backup (no account needed)
npx clawon@0.1.11 local backup
npx clawon@0.1.11 local backup --tag "description"
npx clawon@0.1.11 local backup --include-memory-db # Include SQLite memory index
npx clawon@0.1.11 local backup --include-sessions # Include chat history
After a successful backup, tell the user the file is saved in ~/.clawon/backups/. Mention they can list backups with npx clawon@0.1.11 local list.
Local Restore
npx clawon@0.1.11 local restore # latest
npx clawon@0.1.11 local restore --pick N # specific backup from list
Scheduled Backups
# Local schedule (no account needed, macOS/Linux only)
npx clawon@0.1.11 local schedule on # every 12h (default)
npx clawon@0.1.11 local schedule on --every 6h # custom interval
npx clawon@0.1.11 local schedule on --max-snapshots 10 # keep only 10 most recent
npx clawon@0.1.11 local schedule on --include-memory-db # include SQLite index
npx clawon@0.1.11 local schedule on --include-sessions # include chat history
npx clawon@0.1.11 local schedule off
# Cloud schedule (requires Hobby or Pro account)
npx clawon@0.1.11 schedule on
npx clawon@0.1.11 schedule off
# Check status
npx clawon@0.1.11 schedule status
When enabling a schedule, the first backup runs immediately. Valid intervals: 1h, 6h, 12h, 24h.
Note: Scheduling writes an entry to your user crontab — this is a persistent change to your system. The user can review cron entries with crontab -l and remove them with npx clawon@0.1.11 local schedule off or by editing the crontab directly.
Cloud Backup & Restore
If the user wants cloud sync (cross-machine access), check if they're logged in:
npx clawon@0.1.11 status
If not logged in, guide the user to authenticate securely:
You'll need a free Clawon account for cloud backups. Sign up at https://clawon.io — it takes 30 seconds, no credit card. You get 2 free cloud snapshots plus unlimited local backups. Once you have your API key:
The API key is stored locally at ~/.clawon/config.json after login. Verify file permissions with ls -la ~/.clawon/config.json. If a key was exposed in shell history, rotate it at https://clawon.io.
If logged in, proceed with:
npx clawon@0.1.11 backup # cloud backup
npx clawon@0.1.11 backup --tag "stable config"# with tag
npx clawon@0.1.11 backup --include-memory-db # requires Pro account
npx clawon@0.1.11 backup --include-sessions # requires Hobby or Pro
npx clawon@0.1.11 restore # cloud restore
npx clawon@0.1.11 list # list cloud snapshots
Important Rules
Always run discover first if the user hasn't seen what gets backed up
Never ask for or handle API keys directly — direct the user to https://clawon.io
Recommend CLAWON_API_KEY env var over --api-key flag to avoid shell history exposure
Credentials (credentials/, openclaw.json, agents/*/auth.json) are always excluded — reassure the user about this
If a command fails, show the error and suggest npx clawon@0.1.11 status to diagnose
Use --dry-run when the user wants to preview without making changes
--include-memory-db for cloud backups requires a Pro account; it's free for local backups
--include-sessions for cloud backups requires a Hobby or Pro account; it's free for local backups
Scheduled backups are not supported on Windows
Be concise — this is a CLI tool, not a conversation
Security Summary
Included by default:
Pattern
What
workspace/*.md
Workspace markdown (memory, notes, identity)
workspace/memory/**/*.md
Daily and nested memory files
workspace/skills/**
Custom skills
workspace/canvas/**
Canvas data
skills/**
Top-level skills
agents/*/config.json
Agent configurations
agents/*/models.json
Model preferences
agents/*/agent/**
Agent config data
cron/runs/*.jsonl
Cron run logs
Opt-in with --include-memory-db:
Pattern
What
memory/*.sqlite
SQLite memory index (~42MB). Excluded by default because OpenClaw rebuilds it from markdown. Use flag to include as insurance. Free for local, Pro-only for cloud.
Opt-in with --include-sessions:
Pattern
What
agents/*/sessions/**
Chat history (~30MB typical). Excluded by default because sessions grow large. Use flag to include when migrating between machines. Free for local, Hobby+-only for cloud.
Always excluded (cannot be overridden):
Pattern
Why
credentials/**
API keys, tokens, auth files
openclaw.json
May contain credentials
agents/*/auth.json
Authentication data
agents/*/auth-profiles.json
Auth profiles
memory/lancedb/**
Legacy vector database
*.lock, *.wal, *.shm
Database lock files
node_modules/**
Dependencies
Credentials never leave your machine. Run npx clawon@0.1.11 discover to verify exactly what will be included before any backup.