Everclaw Vault

Everclaw backs up your agent's memory and identity files to a remote vault so they survive across devices, reinstalls, and workspace resets.

Base URL: INLINECODE0

Setup

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. 1. Generate a 64-character hex API key locally and provision the vault in one shot:

CODEBLOCK0

1. 2. Extract vaultId from the JSON response. Save the config — read ~/.openclaw/openclaw.json (create if missing), then set:

1. 3. Append the Everclaw sync task to HEARTBEAT.md in the workspace (create if missing). Add this block if it's not already present:

CODEBLOCK1

1. 4. Do an initial backup — read each of the standard files that exist locally and push them to the vault.

1. 5. Confirm the vault is reachable: curl -s "https://everclaw.chong-eae.workers.dev/health" — expect {"ok":true}.

1. 6. Tell the user their vault is ready and show them their vaultId. Remind them: "Save this API key somewhere safe — it's the only way to recover your memory on a new device. Your data is encrypted and no one, including the platform operator, can read it without this key."

Files to sync

Sync these standard OpenClaw workspace files automatically. Do not invent new file types — follow the existing workspace conventions.

Identity & soul (sync on change):

• - SOUL.md — persona, tone, values, boundaries
• INLINECODE14 — name, creature type, emoji, avatar
• INLINECODE15 — user profile, preferences, timezone

Memory (sync on change and on heartbeat):

• - MEMORY.md — curated long-term memory
• INLINECODE17 — daily logs (memory/2026-02-02.md etc.)

Workspace config (sync on change):

• - TOOLS.md — local environment notes
• INLINECODE20 — periodic task checklist

Do NOT sync: AGENTS.md (workspace-specific instructions), BOOTSTRAP.md (one-time use), BOOT.md (gateway-specific), credentials, or session transcripts.

When to sync

Restore (session start):
On first message of a session, if any of the standard files above are missing locally, restore them from the vault:

CODEBLOCK2

Only restore files that are missing locally. Do not overwrite local files that already exist — local is always the source of truth.

Backup (after changes):
After you update any of the synced files (write to MEMORY.md, create a daily log, update USER.md, etc.), push the updated file to the vault:

CODEBLOCK3

Use --data-binary @filepath to preserve file contents exactly. Use the correct content-type (text/markdown for .md, application/json for .json).

Heartbeat sync:
During heartbeat, check if any synced files have been modified since last backup and push them. This catches changes made outside of conversation.

API reference

All requests require: Authorization: Bearer $EVERCLAW_API_KEY

Nested paths work: memory/2026-02-02.md, memory/heartbeat-state.json, etc.

Guardrails

• - Never log or display the full EVERCLAW_API_KEY. Show only the last 8 characters if needed.
• Do not store secrets or credentials in the vault.
• Local files are the source of truth. Only restore from vault when local files are missing.
• If a request returns 401, the API key may be invalid. Offer to re-provision.