The memory that doesn’t belong to the model
Start in one AI. Continue in another. Finish in a third. Your work carries.
Every session with an AI starts from nothing. You explain again. You paste the same context. The good conversation you had last month is gone, and the version of you it knew is gone with it.
1,062 memories · 433 associations · as of 2026-08-31
project: muninn-dev tags: core-ref · positioning · decided Muninn is the deterministic ground under non-deterministic minds. Things with identity that return verbatim, that nothing rewrites behind the author, reachable by every mind that asks.
Memory, records, artifacts. One idea at three grains.
All three are things with identity that any mind can pick up and put down.
Muninn is where that stops being true. It holds the record between sessions and between tools, so the work accumulates instead of resetting. A specification written in June shapes work in August with no conversation joining them.
Any single session mostly does not need this. A practice across months does not exist without it.
Memory
A thing you told it. Tagged, scoped to a project, searchable by meaning rather than by keyword.
Record
A row in a table you defined, with fields. Private fields your AI can read and a shared view cannot.
Artifact
Something a model made. A document, a diagram, a page. Rendered in the browser, with a link you can send.
Artifacts render rather than sit as source. Diagrams draw. Pages run, on an isolated origin that holds no session and no key, so a page written by a model cannot reach anything of yours.
This is the product. Not memory with extras attached.
What the three of them do is the rest of it: a memory that comes back on the day it matters, a table published as a page you can hand to someone, a bundle a team works from, and the whole store encrypted at rest under a key your own credential unwraps. Sixteen things ship today. They are these three, doing more.
Who holds the pen
Your AI reads this memory and writes to it. It never rewrites it behind you.
No background consolidation. No overnight synthesis. Nothing that merges two of your records into one while you sleep and hands you the result as fact.
| Who writes | The system, on its own schedule, from your transcripts. | You and the AI you are talking to, while you are there. |
|---|---|---|
| On reread | A summary of what it decided the record meant. | The record, word for word, as it was written. |
| If you leave | It stays in the app that built it. | Export it, or read it in the next model tomorrow. |
Three steps, then stop thinking about it
There is nothing to run, nothing to host, and nothing to keep open in a tab.
Add the connector in Claude, pointing at
munn.is/mcp.Sign in once. The connector holds the session; your key never touches a chat.
Say what you want remembered.
Muninn is in daily use by one person, on real work. That is the honest state of it. If that is the kind of thing to be early to, leave an email address below.