> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/resources-context/workspace-memory.md).

# Workspace memory

This article explains the **Memory** feature in the **Resources and Context** tab. Workspace memory is durable, workspace-scoped knowledge that Genesis agents record through chat, workflows, and MCP. Knowledge that should outlive a single task is captured as facts, decisions, conventions, and gotchas, and current memories are automatically included as context in later chat conversations and workflow runs.

## Prerequisites

| Action               | Required role |
| -------------------- | ------------- |
| View the memory list | All members   |
| Archive a memory     | Admin / Owner |

## Types of stored knowledge

Workspace memory is organized into four kinds.

| Kind       | Description                       |
| ---------- | --------------------------------- |
| Fact       | A fact about the project          |
| Decision   | A decision the team made          |
| Convention | A rule or convention to follow    |
| Gotcha     | An easy-to-miss pitfall or caveat |

Each memory has a valid-from date and an optional valid-until date, and shows one of the following statuses.

| Status     | Description                                                       |
| ---------- | ----------------------------------------------------------------- |
| Current    | The memory is valid right now                                     |
| Scheduled  | The valid-from date hasn't arrived yet                            |
| Historical | The valid-until date has passed and the memory is no longer valid |

A memory can also show a relationship to an existing memory: **updates** (replaces the prior memory) or **extends** (both remain valid).

{% hint style="info" %}
Workspace memory can't store credentials or private keys. Content matching those patterns is rejected when you save it.
{% endhint %}

## How Genesis uses it

Genesis agents read and write workspace memory through three paths: chat, workflows, and MCP.

* **Chat and workflows**: Agents search for relevant knowledge with the `recallMemory` tool and record knowledge that should outlive the current task with the `writeMemory` tool. Current memories are also automatically added to the conversation or workflow run context, where agents treat them as evidence.
* **MCP**: External clients can read and write the same memories with the MCP `recall_memory` / `write_memory` tools, or use the `consult` tool to get an answer grounded across the whole workspace — memory plus specs, code, files, workflows, and run history.

## Viewing memories

1. On the workspace page, select the **Resources and Context** tab.
2. Select the **Memory** tab.

The list shows each memory's kind, status, content, valid period, source (chat, workflow, or MCP) and author, and the date it was recorded.

## Archiving a memory

1. On the **Memory** tab, click **Archive memory** (the trash icon) in the row of the memory you want to archive, then click **Archive memory** in the confirmation dialog.

{% hint style="warning" %}
Archiving a memory means agents will no longer recall or receive it. This action cannot be undone.
{% endhint %}

## Further reading

* [Resources and context overview](/resources-context/resources-and-context-overview.md)