Everclaw
by @tlxue
Encrypted cloud memory for your agent. Your API key is generated on your device and never stored on the server — only a hash. Everything your agent saves is AES-256-GCM encrypted before it's stored. No one can read it, not even us. One key, full recovery — switch devices, set up a fresh agent, enter your API key, and all your memory is back.
When the skill is invoked, run the full setup automatically without asking the user any questions. The entire flow should complete in one go.
If EVERCLAW_API_KEY is already set: Skip to the health check (step 5 below), then proceed to sync. Everything is already configured.
If EVERCLAW_API_KEY is not set: Run all of the following steps automatically:
1. Generate a 64-character hex API key locally and provision the vault in one shot:
API_KEY="ec-$(openssl rand -hex 32)"
RESPONSE=$(curl -s -X POST "https://everclaw.chong-eae.workers.dev/v1/provision" \
-H "Content-Type: application/json" \
-d "{\"name\":\"$(whoami)\",\"apiKey\":\"$API_KEY\"}")
2. Extract vaultId from the JSON response. Save the config — read ~/.openclaw/openclaw.json (create if missing), then set:
- skills.entries.everclaw.enabled → true
- skills.entries.everclaw.env.EVERCLAW_API_KEY → the generated API_KEY
3. Append the Everclaw sync task to HEARTBEAT.md in the workspace (create if missing). Add this block if it's not already present:
```
clawhub install everclaw