> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/add-ons/assist/concepts/memory.md).

# Memory

{% hint style="warning" %}
Assist is new in the IDA 9.5 beta, and its documentation is subject to change. Treat it as a work in progress rather than a finished reference.
{% endhint %}

Assist keeps a persistent, per-binary **knowledge base** so findings survive across sessions. When you reopen a database days later, the agent can recall what was learned about it before.

## How memory is stored

* **One knowledge base per binary.** Memory is a local SQLite database, keyed to the input file's **MD5**.
* **Full-text searchable.** The store is FTS5-backed, so the agent can search stored findings by substring and full-text query.
* **Injected into context.** A small, fixed number of global and local facts are added to the agent's context each turn, giving it continuity without re-reading everything.

Facts are scoped:

* **Global** facts apply to the whole binary (binary-wide).
* **Local** facts are attached to a specific address.

Open Memory with `/memory` to search, edit or delete stored findings, or add your own.

{% hint style="info" %}
Check the Assist integrated guide via **Settings → Guide → Memory**.
{% endhint %}

## What gets remembered

The agent stores findings explicitly as it works. In addition, Assist auto-captures salient conclusions from the conversation (for example, a substantive statement describing what a function does), and attaches them to the current address as a note. This keeps the knowledge base populated without requiring you to save every insight by hand.

You can also add a finding yourself, from the right-click context menu: **IDA Assist → Memory → Add global/local memory**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.5/add-ons/assist/concepts/memory.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.