One day, one feature: Mini Me and its "long-term" memory

Initially, I developed this feature to debug Mini Me. When the agent behaves strangely, to understand some "endless loops", ...

Enable the "sessions" feature

It's very simple, you just need to add this to the agent's configuration:

sessions:
  enabled: true
  dir: .mm/sessions

✋ Important: don't forget to add .mm/ to your project's .gitignore.

Now, all your conversations with your agent will be saved in timestamped JSON files, like this:

{
  "id": "20261008-140000-b2c3d4e5",
  "cwd": ".",
  "createdAt": "2026-10-08T14:00:00Z",
  "updatedAt": "2026-10-08T14:35:00Z",
  "messages": [
    {
      "role": "system",
      "content": [
        {
          "text": "You are Bob, the assistant of the bookshelf project."
        }
      ]
    },
    {
      "role": "user",
      "content": [
        {
          "text": "Postgres or SQLite for the storage?"
        }
      ]
    },
    {
      "role": "model",
      "content": [
        {
          "text": "SQLite: one user, nothing to run beside the app. The file is data/bookshelf.db, opened with modernc.org/sqlite (pure Go, no cgo)."
        }
      ]
    },
    {
      "role": "user",
      "content": [
        {
          "text": "How do we handle schema changes?"
        }
      ]
    },
    {
      "role": "model",
      "content": [
        {
          "text": "Plain SQL files in migrations/, numbered: 001_init.sql, 002_add_rating.sql… applied in order at start-up, the last one applied stored in a schema_version table."
        }
      ]
    }
  ]
}

What do we get out of it?

Once session persistence is enabled, you can see the list of previous sessions with the /sessions command:

But you also get the ability to reload the last session into memory, or a specific one by its id, with the /resume command:

It's also the ability (dead simple but really handy) to recall your last questions using the up and down arrow keys.

If you want to scroll through the content of your conversation, use the Tab key.

But that's not all 😉

Do you remember?

If you change your configuration as below, your model will be able to search the memory of its sessions:

sessions:
  enabled: true
  dir: .mm/sessions
  autoSearchMemory: true

The search triggers a new "builtin" tool: search_memory:

You can also enable searchMemory: true and you'll get a new /memory command. But the result of /memory is only for you: the model isn't called, the history isn't modified, so the model never sees these results. Still, it helps you spot the ID of the relevant session(s).

You can get a complete example here: /04-memory

That's all for today. Happy Sunday.