Agent Memory

Help Agent Builder
1

is there an agent memory, else than the memory of the same conversation?
I found in a post linkedin that the agent has a memory of context, but the agent read the contexte each time that it runs
it has also a long memory
I don’t understand the mechanism behind this

image
image1575×709 162 KB

2

Hi @Sal23

The confusion is understandable, “memory” gets used for many different things.

The thing to remember is that the agent itself never remembers anything. An LLM starts from blank on every single run. So “memory” in any agent is never the model recalling, it’s the system storing something and feeding it back in as text at the start of the run.

Three things get called “memory” which your image speaks about:

  1. Conversation memory: the messages within one session. Disappears when the session ends. This is the one you already understand.
  2. Context: the instructions and any data passed into the agent. This is re-supplied every run, which is the “reads context each time” behaviour. It’s being told the same things again, not remembering them.
  3. Long-term memory: a separate persistent store (a database/vector store) that remains the same across runs. The agent writes to it during a run and retrieves from it on later runs. This is what creates consistency between separate conversations.

Remember, long-term memory usually isn’t loading everything every time. It’s selective retrieval. The store might hold hundreds of past records or whatever, but on each run only the ones relevant to the current input get pulled back and added to the context.

Hope this makes sense.

3

Thank you for your answer,
so there is no context memory as i understood,
for the long memory, can I access it ? can I visualise it?
how can I know if the solution is using it or not ? (I don’t use escalation)

4

@Sal23

only escalations are stored in agent memory an you would see the option only then…if you need to maintain a separate one you specifically need to write that data to storage bucket or any vector DB and use it..

and the agent memory that comes from escalations cannot be seen or modified

cheers