# How memory works in Agentic Studio

### Overview

Memory allows Digital Workers to retain and apply knowledge across interactions rather than treating each task as a fresh start. Without memory, a Digital Worker processes every request in isolation, with no awareness of prior context, past decisions, or accumulated operational experience. With memory, a worker can build continuity over time, applying what it has learned from previous interactions to improve the consistency and quality of its work.

Agentic Studio organizes Digital Worker memory into a structured three-plane architecture that separates different types of retained knowledge so each can be stored, accessed, and applied appropriately.

### Memory Maps

Memory in Agentic Studio is organized through Memory Maps. A Memory Map is the structured representation of everything a Digital Worker retains across interactions. Rather than storing all knowledge in a single undifferentiated store, Memory Maps separate retained knowledge into three distinct planes, episodic, procedural, and semantic, each designed to hold a different type of information and serve a different purpose during task execution.

This structure is what makes retained knowledge usable rather than simply stored. When a Digital Worker draws on memory, it pulls from the appropriate plane depending on what the task requires: what happened before, how similar work was completed, or what the business context means.

### The Three Memory Planes

#### Episodic Memory

Episodic memory stores specific interactions and events. It allows a Digital Worker to remember what happened in prior sessions, who it interacted with, what decisions were made, what actions were taken, and what outcomes resulted.<br>

This gives the worker continuity across time. When a case, asset, or user has a history of prior interactions, the worker can respond with awareness of that context rather than starting from zero. Prior escalations, earlier resolutions, and past conversations tied to the same record are all available through episodic memory.

#### Procedural Memory

Procedural memory stores learned procedures and workflows. It captures the patterns, sequences, and operational approaches that have proven effective for similar tasks.

This allows the Digital Worker to retain the how of work, resolution flows, approval paths, escalation patterns, and recurring execution steps, and apply them more consistently over time. Rather than reasoning through a familiar process from scratch on each occasion, the worker can draw on established procedural knowledge to operate more efficiently and reliably.

#### Semantic Memory

Semantic memory stores general knowledge and concepts. It allows the Digital Worker to retain domain knowledge, business rules, entity relationships, and conceptual understanding of the environment it operates in.

This includes information such as policies, operating thresholds, site hierarchies, vendor relationships, and business definitions. Semantic memory enables the worker to reason using durable, context-specific knowledge rather than relying only on what is present in the current session.

### How the Three Planes Work Together

Each memory plane serves a distinct function, but they work together during task execution. Episodic memory tells the worker what has happened before. Procedural memory tells it how similar situations have been handled. Semantic memory tells it what the relevant business context means.

A Digital Worker handling a recurring issue, for example, can recognize the case from prior interactions through episodic memory, apply the resolution approach that has worked before through procedural memory, and reason about the business rules and thresholds involved through semantic memory. The result is a worker that operates with increasing judgment and consistency as it accumulates experience.

### Memory and Continuous Improvement

Memory is the foundation of how Digital Workers improve over time. Each interaction contributes to what the worker retains, and that retained knowledge shapes how it approaches future tasks. This is distinct from one-time configuration. Rather than being defined entirely at setup, a worker's effectiveness can grow as it encounters more situations, resolves more cases, and refines its understanding of the operational environment.


---

# Agent Instructions: 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:

```
GET https://kb.theloops.io/agenticstudio/resource-library/hidden-core-concepts/how-memory-works-in-agentic-studio.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.