---
title: Memory Types and Scopes
description: Choose where a memory applies, what it represents, and how strongly Runner should weigh it.
---

Scope prevents a fact from reaching the wrong work, while Type and Importance help Runner interpret it. Use this page when a memory should apply to more than one task but not necessarily every store or person.

**Entry path:** **Control Center → Agent → Memory → Add a memory**, or open an existing memory to edit it.

## What this covers

You will be able to choose the narrowest correct scope, classify a memory, and use tags and importance without storing sensitive data.

## Availability and prerequisites

- Unified Memory must be enabled for the account.
- Open **Control Center → Agent → Memory → Add a memory**, or edit an existing memory.
- Do not use any scope for passwords, API keys, card data, authentication codes, or other secrets.

## Scope choices

| Scope | Use it when | What happens next |
| --- | --- | --- |
| **This store** | The fact is specific to the current storefront, catalog, brand, or workflow. | Runner groups the memory under the store scope and can apply it to work for this store. |
| **Personal** | The fact describes your own working preference. | Runner groups it as Personal rather than sharing it as a workspace-wide rule. |
| **Organization** | The fact is an approved rule or convention shared across the workspace. | Runner groups it under Organization so it can inform work beyond one store. |

Choose the narrowest scope that is still useful. A store-specific shipping rule, for example, should not be an Organization memory unless it truly applies everywhere.

## Type choices

| Type | Good use | Example |
| --- | --- | --- |
| **Preference** | A desired style or working choice | “Use concise, editorial product descriptions.” |
| **Correction** | A fact Runner previously got wrong | “The returns window is stated in the approved policy document.” |
| **Convention** | A repeatable naming or formatting rule | “Use sentence case for collection headings.” |
| **Knowledge** | A stable business or product fact | “The flagship collection is called Studio Essentials.” |
| **Decision** | An approved choice that future work should respect | “Keep guest checkout enabled.” |

Do not include a secret in an example or memory. Refer to the location of a protected credential instead of storing its value.

## Importance and tags

| Control | Why it is useful | What happens next |
| --- | --- | --- |
| **Low** | Keep a helpful but optional fact available. | Runner gives it less weight when information competes. |
| **Medium** | Use the normal priority for stable working facts. | Runner gives it the default middle weight. |
| **High** | Mark an important approved rule or decision. | Runner gives it more weight when choosing between relevant memories. |
| **Tags** | Make search and grouping easier. | Comma-separated tags are saved with the memory; at least one is required. |

Importance is a priority hint, not an instruction to ignore the current request, account permissions, or safety restrictions.

## Classify a memory

1. Write the fact as one clear sentence.
2. Ask where it should apply: only this store, only to you, or across the organization.
3. Select the closest Type based on why the fact exists.
4. Add a small set of specific tags.
5. Start with Medium importance unless there is a clear reason to choose Low or High.
6. Save and confirm the row appears under the expected scope heading.

## States and limits

- The default new memory uses **This store**, **Preference**, and Medium importance.
- The list displays Type, Scope, how many times the memory was used, and a relative recent-use time.
- Editing Scope moves the memory to a different group after the save succeeds.
- Memory selection depends on relevance and priority; a High memory is not guaranteed to appear in every response.

## Troubleshooting

- If a memory influences the wrong store, change its Scope to **This store** in the correct project.
- If two memories conflict, edit or delete the outdated one instead of raising both to High.
- If search misses a memory, try words from its Content or Tags, then clear the filter.
- If a shared convention is not visible to collaborators, confirm it was saved as **Organization**, not Personal.

## Related guides

- [Add and edit Memory](./memory)
- [Agent Customization overview](./)
- [Security and sessions](../account-and-settings/security-and-sessions)