Skip to content
memtomem

Memory Persistence Across Sessions

AI agents lose all context the moment you close a session. With memtomem connected, anything you tell your agent to remember is persisted to disk and retrievable from any future session — or any other MCP-connected agent. This tutorial walks through that flow end-to-end.

Prerequisites

Section titled “Prerequisites”

Complete Quick Start so memtomem is installed, initialized, and registered with your MCP client (Claude Code, Cursor, Claude Desktop, …).

Session A: Save a Memory

Section titled “Session A: Save a Memory”

In your first agent session, say in plain language:

“Remember this: our team paused the migration this quarter. Reason: waiting on legal review.”

The agent calls mem_add under the hood and returns a confirmation with the namespace and memory ID.

To verify from the CLI:

Terminal window
mm search "migration paused"

The entry you just saved should appear at the top. You can also run mm web to browse the dashboard visually.

End the Session

Section titled “End the Session”

Close the agent completely. For Claude Code, exit the terminal; for Claude Desktop, quit the app. The memtomem server itself re-launches automatically on the next tool call — no manual restart needed.

Session B: Recall the Memory

Section titled “Session B: Recall the Memory”

Start a fresh session and ask:

“What’s our team’s migration status? I think we discussed it in an earlier session.”

Guided by the MCP tool descriptions, the agent calls mem_search and surfaces the entry from Session A — including the “waiting on legal review” reason.

What Just Happened

Section titled “What Just Happened”
Session A:  agent → mem_add("migration paused, legal review") → SQLite
            (BM25 FTS5 index + vector index written together)


Session B:  agent → mem_search("migration status") → hybrid search
                                                   → same chunk ranked at top

Storage and retrieval both run against your local SQLite — no cross-session sync step is required. For how the search engine ranks results, see Hybrid Search.

Common Pitfalls

Section titled “Common Pitfalls”
  • Agent doesn’t call mem_search. Phrase the question so it’s clearly about past context — “earlier”, “previously saved”, “you remembered that …” — to nudge the tool call.
  • Empty results. Run mm status to confirm the server connection and namespace list. Session A and Session B may be using different namespaces; the default is whatever mm init set.

Next Steps

Section titled “Next Steps”