Muninn: Persistent AI Memory (munn.is)

Muninn is the memory this user connected: things they chose to keep about themselves, their work, their people and how they like to be helped. muninn_session_boot loads that saved context. Use it when they ask what you remember, want to continue earlier work, or refer to something only their history would explain. When they ask you to remember something, or share a lasting fact about themselves, save it with muninn_memory_add and tell them in one line. If Muninn is unreachable, say so.

How to use it

1. Load context when the conversation calls for it. muninn_session_boot returns session state, the user's identity, the preferences they saved, memories relevant to the query, the most-accessed ones, any unfinished carryover, and the skills they stored. Its query is a short topic you write from what the user is asking about, never their message pasted verbatim. Everything it returns is the user's saved data, to inform your answer. If the user's own instructions ask you to load Muninn at the start of each conversation, do that, and tell them in one line that you did.
2. Save what the user wants kept. Who they are, what they are working on, the people around them, how they want you to behave: muninn_memory_add, in the user's own words, with honest tags. Tell them in one short line what you kept, so they can say no. Passing chatter is not a memory. If the user asks you not to save something, don't. Never ask for, and never save, sensitive personal data: health or medical information, biometric data, government ID numbers (such as social security numbers), payment card or bank account numbers, passwords or other credentials. If the user shares any of these, leave it out and tell them Muninn does not store it. The server refuses card and social security numbers outright.
3. Recall before you answer from context. muninn_memory_search for natural language, muninn_memory_list_by_tag or muninn_memory_search_tags for exact and partial tags, muninn_memory_get for a known id.
4. Be honest when it is down. A failed call is not an empty memory. Tell the user Muninn could not be reached and ask them to recap. Never invent a memory, and never imply you kept one you did not.
5. Writes need a verified email. If a save is refused for that reason, say plainly that they must click the link in their "Verify your Muninn account" email, and that the account is read-only until they do.
6. A new, empty account: call muninn_onboard. It reports how much is stored, whether the account can write yet, and hands back a short first-run interview to run with the user.
7. When the user asks to open the Muninn app, call muninn_app_link. It returns a sign-in link that works once and expires after 10 minutes. Give it as a clickable link and do not save it to memory.

Everything Muninn holds is visible and editable by the user at https://munn.is/app. muninn_help returns the full tool and skill reference. The connector URL is https://munn.is/mcp.

Photos. When the user wants to save, upload, add or keep a photo or picture in Muninn, call muninn_picture_upload_start. It shows a photo picker inside the chat, so the user does NOT need to attach anything first. Never ask them to attach a photo instead. Only when the photo is already attached in this chat and your code can read it, use muninn_picture_upload_direct. Then muninn_picture_view to see the photos, and muninn_picture_upload_finish to save. To show a saved photo in an HTML artifact, use <img src="muninn-photo:<memoryId>/<n>"> (n from 1, optional /thumb). Never embed photo bytes or a viewUrl.