Walrus Memory release notes

MCP

Walrus Memory MCP v0.0.14

September 22, 2026 | GitHub

Unreleased. The plugin's launcher installs @mysten-incubation/memwal-mcp@0.0.14-dev.0, named by mcpPackageVersion in plugin/plugin.json, until 0.0.14 is on npm; drop that key in that release.

Changes

• The cold-start tool list no longer advertises a tool the relayer may not serve. The bridge ships on npm and updates itself while a relayer ships per environment, so 0.0.14-dev.0 dialled prod and staging still on 0.0.13: cold start named memwal_remember_status, which neither registers, and the pending-write wording sent the agent to go call it — one live run spent 90.67s there before erroring. Cold start is now a floor rather than a forecast (BASELINE_RELAYER_TOOLS): it carries only what the oldest supported relayer serves and its descriptions name nothing outside it, while newer tools still reach the client a beat later on the relayer's own tools/list. Initialize instructions use the same floor (they used to name memwal_remember_status before any tools/list). And a call for a tool outside that floor — including during the cold-start window, before any upstream tools/list has been seen — is now answered locally and at once — naming the tools that do exist and saying plainly that nothing ran — instead of being forwarded into a wait that only ends at the orphan deadline.

---

Walrus Memory MCP v0.0.13

September 15, 2026 | GitHub

Changes

• Unrecognised options now warn on stderr and in the structured log (cli.unrecognised_arg) instead of being dropped in silence, so a typo'd --namesapce work no longer writes to the default namespace with nothing to say it had. The warning names the option key only, keeping a mistyped value-taking flag (--tokenn=hunter2) from putting the secret on stderr, and it warns rather than exits so an option from a newer config cannot brick the server.
• --help now lists the network presets (--prod, --dev, --staging, --local) with the relayer and web URLs each resolves to, rendered from the preset table rather than retyped so a new preset cannot ship undocumented the way --prod did. The --label default is corrected to "MCP Client", which is what the code actually falls back to.
• memwal_health reports relayer=<url>, naming the origin this process dialled, so a client bound to the wrong network finds out there instead of by noticing its memories are missing. The URL is captured when the call is sent rather than when the reply lands, so a reconnect mid-flight cannot label the answer with a relayer it did not come from.
• Keep reading stdin after an in-session memwal_login. The auth-required stub hands off to the bridge by pausing stdin, and a stream paused that way does not resume when a new data listener attaches, so the bridge served only the request replayed from the hand-off and then went deaf. Signing in appeared to work, the retry succeeded, and every call after it hung until the client timed it out.
• Confirm a completed sign-in instead of only writing it to the log file. The failure path already reported itself twice (a notification and a notice on the next tool call) while success reported nothing, so a user who approved in the browser could not tell whether credentials had landed, the bridge had adopted them, or a retry was worth trying. Success now sends the matching notification and prefixes a one-shot banner naming the account, the delegate, and the resolved credentials path onto the next tool result.
• Stop the memwal_login prompt claiming you are already signed in when you are not. The bridge assumed it only ever runs with credentials on disk, but memwal_logout deletes them and login is intercepted before the signed-out guard, so a login after a logout in the same session announced that a stored delegate key would be replaced, reading as though the logout had not taken. Both prompts now read the credentials file instead of assuming the mode.
• Write the credentials file by creating a new 0600 file and renaming it into place, instead of writing the delegate private key to the existing path and tightening the permission afterwards. writeFileSync's mode only applies when it creates the file, so a credentials.json left world-readable by anything outside the CLI (a manual chmod, a restored backup, another tool) received the new key under the old permission until the following chmod landed. The CLI now writes the backup it takes when signing in as a different account the same way; that backup holds the same plaintext key, and the CLI previously created it under the process umask. On Windows, where rename cannot replace a destination another process holds open and POSIX mode bits are not enforced at all, the CLI retries briefly and then writes in place rather than failing the sign-in.

---

Walrus Memory MCP v0.0.12

September 9, 2026 | GitHub

Changes

• Optional maxDistance on memwal_recall: cosine-distance cutoff (low = similar, must be >= 0). Hits with distance >= maxDistance are dropped. Result lines now include both score (1 − cosine distance) and distance.
• Resolve the credential directory on every access instead of freezing it at module load, and let MEMWAL_CREDS_DIR override it. The login test sandboxed the home directory with HOME alone, which os.homedir() ignores on Windows, so running the package's test suite there wrote fixture credentials over the developer's real ~/.memwal/credentials.json and destroyed the delegate key stored in it.

---

Walrus Memory MCP v0.0.11

August 24, 2026 | GitHub

---

Walrus Memory MCP v0.0.10

August 20, 2026 | GitHub

Changes

• Answer orphaned tool calls whose upstream response never arrives with a retryable error instead of hanging indefinitely. The bridge now tracks in-flight request start times and sweeps expired calls through a per-request deadline (MEMWAL_MCP_CALL_TIMEOUT_MS, default 240s), reuses the existing late-reply drop so an expired call cannot get a second response, and enriches reconnect logs with pending request IDs and methods.
• Inject the configured default namespace (--namespace / MEMWAL_NAMESPACE) into memwal_remember_bulk calls that omit one, so bulk facts land in the project namespace instead of the relayer fallback default.
• Send proactive-usage instructions in the MCP initialize handshake, so the model knows when to save and recall without being asked. Clients moved to lazy tool loading, which keeps tool descriptions out of the model's context until a tool is explicitly loaded; the guidance lived only in those descriptions, so the model stopped using memory on its own and would offer its built-in memory or deny the tool existed. instructions travels with initialize, before any tools/list, so lazy loading cannot strip it.

---

Walrus Memory MCP v0.0.8

August 14, 2026 | GitHub

---

Walrus Memory MCP v0.0.7

August 14, 2026 | GitHub

---

Walrus Memory MCP v0.0.6

July 31, 2026 | GitHub

---

Package v0.0.5

June 12, 2026 | GitHub

Adds the automatic memory plugin for Claude Code, Codex, Cursor, and Antigravity, along with new memwal_remember_bulk and memwal_health tools and proactive memory behavior. Also fixes the plugin bundle so it ships .mcp.json correctly.

---

Package v0.0.4

June 5, 2026 | GitHub

Fixes HTTPS dashboard sign-in callbacks and credential reload after login so tools work without restarting the MCP client.

---

Package v0.0.3

June 4, 2026 | GitHub

Rebrands package metadata from MemWal to Walrus Memory throughout the MCP server.

---

Package v0.0.2

May 25, 2026 | GitHub

Adds relayer compatibility checks and rebrands from MemWal to Walrus Memory across the MCP server package.

---

Package v0.0.1

May 15, 2026 | GitHub

Initial release of the MCP server with stdio transport, browser wallet login, and inline session tools. Includes memory tools for remember, recall, analyze, and restore.

---

TypeScript SDK

Walrus Memory TypeScript SDK v0.1.8

September 22, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.7

September 15, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.6

September 9, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.5

August 26, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.4

August 24, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.3

August 20, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.2

August 14, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.1

August 7, 2026 | GitHub

---

Walrus Memory TypeScript SDK v0.1.0

July 31, 2026 | GitHub

---

Package v0.0.7

June 2, 2026 | GitHub

Adds an optional occurredAt parameter to analyze() for temporal anchoring of extracted facts. Relative date references are now resolved into absolute dates.

Changes

• Add optional occurredAt to analyze() and analyzeAndWait() for temporal anchoring of extracted facts.

---

Package v0.0.6

May 28, 2026 | GitHub

Adds RecallParams for object-style recall calls and deprecates the positional recall overload. Also documents restore() response fields.

---

Package v0.0.5

May 25, 2026 | GitHub

Adds relayer compatibility checks, RecallOptions for topK/namespace/maxDistance filtering, and prefers Sui gRPC for SEAL sessions. This release also rebrands from MemWal to Walrus Memory.

---

Package v0.0.4

May 15, 2026 | GitHub

Adds getRememberStatus for polling async job state and SealServerConfig for manual SEAL configuration. Manual mode validates API key pairs.

---

Package v0.0.3

May 8, 2026 | GitHub

Updates remember() for the async relayer flow and introduces rememberAsync, waitForRememberJob, rememberAndWait, and bulk remember helpers. Also adds async analysis with analyzeAndWait.

---

Package v0.0.2

April 30, 2026 | GitHub

Adds per-request nonce signing to block replay attacks and replaces delegate key transport with ephemeral SEAL sessions. SDK versions that do not include a nonce are rejected with HTTP 426.

---

Python SDK

Walrus Memory python v0.1.11

September 22, 2026 | GitHub

Release memwal Python SDK v0.1.11

---

Walrus Memory python v0.1.10

September 15, 2026 | GitHub

Release memwal Python SDK v0.1.10

---

Walrus Memory python v0.1.9

September 9, 2026 | GitHub

Release memwal Python SDK v0.1.9

---

Walrus Memory python v0.1.8

August 26, 2026 | GitHub

Release memwal Python SDK v0.1.8

---

Walrus Memory python v0.1.7

August 14, 2026 | GitHub

Release memwal Python SDK v0.1.7

---

Walrus Memory python v0.1.6

August 7, 2026 | GitHub

Release memwal Python SDK v0.1.6

---

Walrus Memory python v0.1.5

July 31, 2026 | GitHub

Release memwal Python SDK v0.1.5

---

Package v0.1.4

June 2, 2026 | GitHub

A patch release for the Walrus Memory Python SDK.

---

Package v0.1.3

May 28, 2026 | GitHub

A patch release for the Walrus Memory Python SDK.

---

Package v0.1.2

May 25, 2026 | GitHub

A patch release for the Walrus Memory Python SDK.

---

Package v0.1.0

May 21, 2026 | GitHub

Initial release of the Walrus Memory Python SDK.

---

OpenClaw

Walrus Memory SDK v0.0.7

October 2, 2026 | GitHub

---

Walrus Memory SDK v0.0.6

August 20, 2026 | GitHub

and serverUrl as required in configSchema, so OpenClaw rejected the config entry the

---

Package v0.0.5

June 15, 2026 | GitHub

Fixes a workspace dependency that broke npm installs outside the monorepo and switches the release workflow to pnpm publish.

---

Package v0.0.4

June 2, 2026 | GitHub

Adds temporal anchoring through occurredAt to the memory_store tool. The auto-capture hook now passes the current timestamp, and the SDK is bumped for the new AnalyzeOptions.

Changes

• Wire temporal anchoring through the agent-side memory tools.

---

Package v0.0.3

May 25, 2026 | GitHub

Rebrands from MemWal to Walrus Memory across the OpenClaw memory plugin.

---

Package v0.0.2

April 30, 2026 | GitHub

Initial release of the OpenClaw memory plugin with automatic recall and capture hooks, session summary, CLI commands, and LLM tools.

---