> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/for-users/agent-memory.md). # Agent Memory Agents in Blockbrain can now remember you. When you tell an agent something worth keeping — your role, a project you are working on, how you like answers formatted — it can save that as a memory and use it in later conversations, with any agent, without you repeating yourself. You decide whether memory is on, you can see everything it holds, you can add to it, correct it, delete single memories or wipe it entirely. Memory is switched on for your organisation by Blockbrain. If you do not see **Memory** in your account menu, it is not yet enabled for your organisation — contact your Blockbrain Customer Success Manager. ### Where to find it Open your account menu from your avatar in the top-right corner. **Memory** sits in the list of account entries, below API Access. {% embed url="" %} The Memory window has four parts: the on/off switch, an import option, the link to view and manage your memories, and two fields that shape how every agent talks to you — what agents should call you, and your standing instructions.

### Turning memory on and off **Reference saved memories** is your personal switch. When it is on, agents may save memories from your conversations and use them when responding. When it is off, agents stop saving new memories, stop using the ones you already have, and can no longer look anything up in your memory — but your stored memories are kept until you delete them, so you can switch memory back on later without losing anything. The switch is yours alone: it controls memory for your account, not for anyone else. It covers agent memory only. It does not change the knowledge bases, files or data rooms a bot or agent is connected to — those are shared content, not memory about you. ### What agents remember Memory is meant for durable facts about you, not a transcript of your chats. There are three ways a memory is created: * **Learned from chats.** At the end of a conversation turn, the platform picks out facts worth keeping — who you are, what you are working on, preferences and standing instructions you have stated — and stores them. Casual content that will not matter next week is skipped. * **Asked of the agent.** Tell an agent directly: “Remember that I lead the procurement team” or “Forget that I still report to the sales team”. The agent saves or removes the memory and tells you it has done so. If a request to forget matches several memories, the agent asks which one you mean rather than deleting blindly. * **Added by you.** Type a fact into the **Add or update a memory** box in Manage memory, or import what another AI assistant already knows about you (see below). Memories are only captured from your own interactive chats. Automated runs — workflows, scheduled messages — do not read or write your memory, and assistants embedded in websites or apps do not use it either. Your memories are private to you: they are not shared with other people in your organisation, and a memory written in one conversation is never visible to another user. ### How agents use memory Every time you send a message, the agent receives two things in the background: a short profile of you, and the handful of stored memories most relevant to what you just asked. It treats both as background — what you write in the conversation always takes priority. If a question needs more than that, the agent can also search your memory directly, the same way it would search a knowledge base. You can always see what was used. When a reply drew on your memory, the sources panel of that message gains a **From memory** section. Each entry shows whether it is a saved memory or a past chat, when it was captured, and where it came from: memories you typed are marked **Added manually**, memories learned from a conversation show that conversation’s title, and clicking one opens that chat at the message it came from.

### Nickname and instructions for agents Two fields in the Memory window apply to every agent, across all your chats, from the moment you save them — no learning period needed: * **What should agents call you?** — a nickname the agents use when addressing you. * **Instructions for Agents** — tell the agents how to respond: your preferences, role and context, in your own words. “Answer in German, keep it short, I am a controller and care about numbers” is a good example. Press **Save** after editing either field. If you are new to memory, these two fields are the quickest way to get personal answers today; the learned memories build up over time. {% embed url="" %} ### Viewing and managing your memories Click **View and manage memory** to open **Manage memory**. The top of the window shows *the profile the agents see*: a short text with an **Overview** of you, a **Top of mind** section for what you are currently working on, and further sections by topic. It is generated from your stored memories, written in the language you mostly chat in, and is read-only here — to change it, change the memories underneath it. It is refreshed about once a day, and rebuilt straight away when you add or delete a memory yourself (a rebuild takes under a minute, so reopen the window if the text has not caught up yet).

#### Adding or correcting a memory Type a fact into **Add or update a memory…** and press the arrow. The box does two jobs: if the fact is new it is added; if it contradicts or restates something already stored (“I moved to the Munich office” after “I work in the Berlin office”), the old memory is replaced immediately, so a correction takes effect in your next message rather than after the next refresh. Typing something with no fact in it returns “Nothing to remember in that text”; a fact you already have returns “You already have that memory saved”. #### Stored memories Below the profile, **Stored memories** lists every memory in two tabs, each with a live count so nothing is hidden: | Tab | What it holds | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Added by you** | Memories you typed into the box, asked an agent to remember, or imported from another AI assistant. This tab opens first, so you can always check what you deliberately added. | | **Learned from chats** | Everything the platform captured automatically from your conversations. | Use the bin icon on any row to delete that single memory. The profile rebuilds right away.

#### Deleting everything **Delete all memories** at the bottom of the list removes everything memory holds about you: every stored memory, the profile, your nickname and your instructions. It cannot be undone. Your **Reference saved memories** setting stays as it is, and you can wipe your memory even while the setting is off. ### Importing memory from another AI assistant If you have used ChatGPT, Claude or Gemini for a while, that assistant already knows a lot about you. You can bring that over instead of starting from zero: 1. In the Memory window, click **Import** next to *Import memory from other AI providers*. 2. Copy the prompt shown in step 1 and paste it into a chat with your other AI assistant. The prompt asks it to export everything it has stored about you — instructions, facts, preferences and lasting context. 3. Paste the assistant’s answer into the box in step 2 and click **Add to memory**.\ \ `Export everything you have stored about me in memory.` `Rules:` * `Only include what is actually saved in your memory or custom instructions. Do not infer, summarise our current chat, or invent anything.` * `If a category is empty, skip it.` * `Output plain text only, no commentary before or after.` `Group it like this:` #### `About me` `Role, employer, location, languages, anything else stored about who I am.` #### `Work and projects` `Ongoing projects, teams, tools, systems I work with.` #### `How I like answers` `Tone, length, format, language, and any standing instructions I have given you.` #### `People and context` `People, products or terms you have stored that are specific to me.` #### `Other` `Anything saved that does not fit above.` `Write each item as a single short line, one fact per line.` The import runs in the background; you can close the window. The platform extracts individual facts from the pasted text, stores them as memories in the **Added by you** tab, skips duplicates of things you already have, and refreshes your profile. One import runs at a time, and there is a daily limit on imports. {% embed url="" %} ### Memory and your compute blocks Saving, recalling and consolidating memories uses AI processing, and that usage counts towards your compute blocks like any other activity. If you reach your compute-block limit, memory pauses with the rest of the platform: imports and manual additions are declined with the usual limit message, background learning skips your turns, and agents answer without recalled memories until your limit resets. Nothing already stored is lost. ### Tips * Say it plainly. “Remember that…” and “Forget that…” are understood by every agent. * Use **Instructions for Agents** for standing preferences (language, tone, format). Use memories for facts (role, projects, tools you use). * Correct, do not accumulate. Adding the updated fact replaces the outdated one; you do not need to delete first. * Check the profile now and then. It is the shortest way to see what agents assume about you. * Working in a shared or test account? Turn **Reference saved memories** off there, so that account does not build a profile from several people. ### Troubleshooting | Symptom | What to do | | --------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Memory is not in my account menu | Memory is not yet enabled for your organisation. Ask your administrator or Blockbrain Customer Success Manager. | | The agent did not remember something I said | Check that **Reference saved memories** is on. Only durable facts are captured automatically; if something matters, tell the agent to remember it, or add it in Manage memory. | | I added a memory but the profile has not changed | The profile rebuilds in the background and can take up to a minute. Close and reopen Manage memory. The memory itself is already in use by agents. | | I switched memory off but the agent still knows something | Memory off stops saving and recalling across conversations. Within a single conversation the agent still sees everything said earlier in that chat, which is not memory. | | I want to remove one thing the agent knows | Open Manage memory, find it under **Added by you** or **Learned from chats**, and use the bin icon. Or tell the agent “Forget that…”. | | An import did nothing | If the pasted text contained no facts, or only facts you already had, nothing new is added. Check that you pasted the assistant’s answer, not the prompt. One import runs at a time and imports are limited per day. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.blockbrain.ai/for-users/agent-memory.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.