@sovseal/sdk’s local store()/recall() into an ElizaOS agent as a small custom plugin. ElizaOS agents maintain state continuity and can securely sync encrypted snapshots using sovseal’s zero-knowledge, client-side-encrypted replication when you also use snapshot/restore.
By using
sovseal’s zero-knowledge client-side encryption (AES-256-GCM) for the replication path, ElizaOS agents can persist facts and state across restarts without exposing plaintext data to third-party database servers.Installation
Add@sovseal/sdk to your ElizaOS project workspace:
Build a minimal sovseal plugin
ElizaOS plugins are plain objects implementing thePlugin interface — actions (what the agent can do), providers (what the agent can see), services (long-lived connections). Create src/plugins/sovseal-memory.ts:
characters/my-agent.character.json) alongside your other plugins:
store/recall require the native host launcher at ~/.sovseal/native-host/run.sh. Run npx -y @sovseal/mcp-server once to provision it — see SDK Reference: Overview. Consult ElizaOS’s plugin architecture docs for the full Action/Provider interface — the shapes above are illustrative of the pattern, not a copy of ElizaOS’s type definitions.Zero-knowledge state replication (optional)
If you also want encrypted multi-device sync of full agent state (not just semantic recall), use@sovseal/sdk’s snapshot()/restore() methods — see the Node SDK reference for the full API. That path requires an endpoint and apiKey; store/recall above do not.