Tusk

From its catalog listing
Hermes long-term memory on Walrus mainnet (decentralized storage on Sui) through the official Walrus Memory SDK: encrypted inside the relayer's TEE, owned by your key, survives wiping or reinstalling Hermes, and the same on every machine and for other agents on the same account. Recall before each turn, turn capture, built-in memory mirroring and pre-compression saves; a crash-safe, rate-paced SQLite write outbox with a receipt and public Walruscan proof per memory; a Tusk dashboard tab (semantic search across namespaces, live write queue, one-click verification that downloads the blob from a public Walrus aggregator and checks it is ciphertext); /tusk and hermes tusk (status, recall, proofs, verify, namespaces, import, flush, export, restore). Secrets are redacted before anything is queued.
Good to know before installing
each turn's user message (as the recall query), finished turns (for fact extraction), built-in memory entries and tusk_remember facts are sent over HTTPS to relayer.memory.walrus.xyz (or MEMWAL_SERVER_URL) signed with MEMWAL_PRIVATE_KEY / MEMWAL_ACCOUNT_ID; verify downloads blobs from aggregator.walrus-mainnet.walrus.space; queued writes (until sent) and receipts are kept in plugin-data/tusk/outbox.db (0600); one in-process background writer thread; dashboard routes sit behind the dashboard auth gate; no shell commands, no subprocesses, no telemetry.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs (this one needs
MEMWAL_PRIVATE_KEY,MEMWAL_ACCOUNT_ID), then asks whether to turn it on.hermes plugins install tusk - Said no? Turn it on later:
hermes plugins enable tusk - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Memory & notes
- Maintained by
- Automationbot24x7 (Community)
- Needs
MEMWAL_PRIVATE_KEYMEMWAL_ACCOUNT_IDAPI keys- Works on
- linux, macos, windows
- Needs Hermes
- 0.23.0 or newer
- Version
- 0.2.1
- In the catalog
- 2026-11-09
Known issues (from its catalog listing)
- The Walrus Memory relayer has no per-memory delete yet (whole-namespace erasure only), so removing a built-in memory entry does not delete its Walrus copy.
- Writes are paced (about 6 per minute) and take 20-30 s each; one-shot hermes chat -q runs usually exit before the queue drains. Queued writes go out on the next run or with hermes tusk flush.
- The dashboard tab appears after hermes plugins enable tusk (memory providers are otherwise activated through memory.provider only).
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in memory & notes
New Hermes Agent updates every day on X. Follow @HermesWatcher