Store one thing in the user's private, portable memory on Walrus.

Call this the moment something is worth carrying into a future session: a decision, a preference, a fact about the project, or an action taken on the user's behalf. Before the session ends, store one handoff digest (what changed, the state things were left in, what comes next); recall first so the digest supersedes earlier notes instead of duplicating them. The user's identity and passphrase come from your MCP client configuration, not from these arguments, so the note is encrypted for that user without the secret entering the conversation, and the same person recalls it from any device or agent.

stored true means the note is durably saved and will be returned by recall from now on, including from other devices. On false, read note and tell the user instead of assuming it saved.

receipt starting with buffered: is normal and healthy, not a fallback or a degraded mode. Every write lands in a durable write-ahead buffer first and is batched onto Walrus a few hours later, because Walrus charges per write regardless of size, so batching is what makes the service affordable. Do not report a buffered receipt to the user as a failure or as "saved locally only": the note is safe and already recallable everywhere.

Recall what is relevant from the user's portable memory before you act.

Call this at the start of every session, scoped to the project's folder, so you continue from where any previous session (on any machine, in any agent) left off instead of starting from zero. Call it again whenever you need context the user has given before, and before remembering a digest, so the new note supersedes rather than duplicates. The user's identity and passphrase come from your MCP client configuration, not from these arguments, so it decrypts that user's own memory without the secret entering the conversation. An empty list means nothing relevant is remembered yet. When truncated is true the folder holds more than could be scanned, so treat the answer as incomplete and say so.

Forget a folder of the user's memory, permanently. Confirm with the user first.

After this, no recall will return the folder's notes again; the folder starts fresh and new notes work immediately. This is irreversible, so call it only when the user explicitly asks to forget or wipe a folder, never on your own judgement. The server verifies the configured passphrase actually opens the folder before honouring it, so an identity string alone cannot wipe anything. Honest semantics: the old encrypted notes stay on Walrus until their storage expires, sealed under the passphrase; they are simply never served again.

List the files the user has stored in a folder (name and size).

Files are stored separately from notes, so recall never returns them. Call this to see which files exist, then fetch_file to retrieve one. Returns each file's name and size. An empty list means no files in that folder yet; locked true means the passphrase does not open them.

Retrieve one of the user's stored files, decrypted, by name.

Files live separately from notes. Call list_files first to find the name. Returns the file's bytes as base64 in data_base64 along with its name and content_type; to save it, decode the base64 and write the bytes to disk (for example echo <data_base64> | base64 -d > <name>). Very large files are not inlined; retrieve those from the web console or the REST /file/download endpoint instead.