Walrus Memory plugin
A plugin with an MCP server: the agent saves decisions and preferences to encrypted Walrus memory and recalls them later.
- 137 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The agent writes facts to immutable storage, so they cannot be deleted later.
- Sign-in needs an account and wallet confirmation.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/walrus-memoryDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent writes facts to immutable storage, so they cannot be deleted later.
- Sign-in needs an account and wallet confirmation.
This is third-party code. Review the repository files before installing.
What it does
Walrus Memory (MemWal) is a long-term memory layer for agents. The plugin for Claude Code, Codex, Cursor and Antigravity adds an MCP server with the tools `memwal_remember`, `memwal_recall`, `memwal_namespaces`, `memwal_analyze`, `memwal_restore`, `memwal_health`, `memwal_login` and `memwal_logout`. Lifecycle hooks remind the agent to save durable facts and to use this memory before the built-in one. Memories are encrypted and stored on Walrus, while owner rights are enforced by a contract on the Sui network. Every operation runs inside an owner plus namespace boundary, so projects do not mix. The same MCP server can be connected to any client without the plugin, but automatic saving is then absent.
Who it is for. Developers whose agent forgets agreements between sessions and apps and who want memory under their own control.
Good fit when
- A new session needs the stack, code style and earlier project decisions.
- The same preferences are needed in Claude Code and in Codex.
- Several agents work on one task and share memory through a namespace.
- Accumulated local memory is moved into a single account.
Not a fit when
- Context matters only inside the current session.
- Data must not leave for external storage, even encrypted.
- Saved facts will need deleting later, but Walrus storage is immutable.
Example request
Recall which architecture decisions for this project were saved earlier, and remember that project answers are written in Russian.Limitations
The project is in beta. Sign-in needs a Walrus Memory account: the agent calls `memwal_login` and hands over a confirmation link. Saved data cannot be deleted. The plugin strips passwords, API keys, tokens and seed phrases before writing, but other text is stored as is, so do not ask the agent to remember private data. Node.js 22.23.4 or newer from the 22 line (or 24.22.1 or 26.12.1 and newer) and a Claude Code version with plugin support are required.
How to disable. Disable the plugin in the client's plugin manager. Turn off only automatic saving with `memwal-mcp auto-save off` or `MEMWAL_AUTO_SAVE=0` in the client's `env` block. Anything already written to Walrus stays.
FAQ
How does the plugin differ from a plain MCP server?
The plugin adds lifecycle hooks that remind the agent to save facts and prefer `memwal_*` over built-in memory. The MCP-only setup gives tools alone, and automatic behavior depends on the client and model.
How do I connect it to Codex?
Run `codex plugin marketplace add MystenLabs/MemWal`, then `codex plugin add memwal@memwal-plugins` and trust the hooks through `/hooks`.
How do I stop saving without being asked?
Use `memwal-mcp auto-save off` or `MEMWAL_AUTO_SAVE=0` in the client's `env` block. An explicit request to remember something keeps working.
Which data never reaches memory?
Passwords, API keys, tokens, private keys, seed phrases, authorization headers and URLs with `user:password` are stripped before writing.
Is an account required?
Yes. A Walrus Memory account is created during sign-in at memory.walrus.xyz. After `memwal_login` credentials sit in `~/.memwal/credentials.json`, and client configuration files carry no keys.
Discussion
No questions or reviews yet.
Related
PluginsA long-term memory plugin that keeps decisions, preferences and task state across sessions and injects only what a query needs
Long-term memory for Claude Code, Cursor and Codex: the agent saves decisions and finds them again in later sessions
Long-term memory for agents: a remote MCP server, plugins for Claude Code, Cursor and Codex, and an API for your own apps
Agent memory as a graph of linked facts: decisions and errors outlive the session, with no vector database or paid API calls
LongMemory keeps project memory in local SQLite and serves it to an agent over MCP: decisions, task state, skills and a code graph
A long-term memory MCP server for AI agents: facts fade along a forgetting curve and related records are compressed into a summary
Comparison with similar tools
Cards that share the main search query, and how they differ.
README in short
The repository holds the `@mysten-incubation/memwal` SDK, an app, a relayer and plugins. For agents there is a separate `SKILL.md`, MCP documentation for each client and an OpenClaw plugin.