Memory

Beyond a conversation, the agent keeps a small, readable memory about you and your work. Unlike a session's history, memory persists between sessions.

Imaginne has two memories, with different scopes:

	Project memory	Account memory
Where	Desktop, TUI, VS Code	Web chat
Scope	One project (workspace)	You, across every web chat conversation
Format	Four Markdown files on your disk	Short cards, stored on the server
Who edits	You and the agent	You (the agent suggests; you approve)

The rest of this page describes project memory. For account memory, see Account memory.

Four notes, per project

Memory is four Markdown files in .imaginne/memory/, read at the start of each session.

Memory lives in <project>/.imaginne/memory/ as four Markdown files:

Note	What it's for
User profile	Who you are, your role, your work preferences.
Project memory	The project's goals, context, and current state.
Glossary	Terms and acronyms from your domain.
Decisions	What was agreed and why — a decision log.

They are per workspace (per project), not global. They are ordinary files: you can read and edit them.

How the agent uses memory

• At the start of the session, the four notes enter the model's context, in a stable order (profile → project → glossary → decisions).
• During the conversation, the agent can update the memory when it notices a preference, a correction, or a decision. Changes are written to disk immediately.

Changes take effect in the next session

The system prompt is assembled from a snapshot taken at the start of the session. Because of that, a memory update made mid-conversation only starts to influence the agent in the next session. This keeps behavior stable and predictable within the same conversation.

Protections

Memory is handled with care because it feeds the system prompt:

• Atomic writes and a file lock prevent corruption when there are concurrent edits.
• External-change detection: if a file was modified outside Imaginne, it makes a backup and flags it, instead of blindly overwriting.
• Injection check: every write goes through a check that blocks prompt-injection attempts and invisible/bidirectional characters before they reach the system prompt.

Editing memory

• Desktop — open Project Memory in the side navigation. The notes open in read mode; edit and save.
• Terminal (TUI) — use /memory (/memory <user|project|glossary|decisions|review|list>) to view or review.
• Web chat — the Memory item in the sidebar manages the account memory (cards, suggestions, and limits). See Account memory.

On the local surfaces you can also edit the .md files directly — they're yours.

Memory ≠ session

	Session	Memory
Scope	One conversation	The project, across conversations
Content	Messages and actions	Profile, project, glossary, decisions
Affected by clearing context?	Yes (forgets the history)	No

See also

💬Sessions

What happens inside a conversation.

Open →🧠Account memory

What Imaginne remembers about you in the web chat.

Open →🔒Security & privacy

How content is handled before it goes to the model.

Open →