> ## Documentation Index
> Fetch the complete documentation index at: https://guides.runner.now/llms.txt
> Use this file to discover all available pages before exploring further.

# Memory

> See, edit, and organize the facts and preferences Runner can use across sessions.

Personal Memory is where Runner keeps durable facts and preferences your AI employees can use across jobs and sessions.

* *"Keep my email drafts to three sentences max."*
* *"Sarah and James are always high priority."*
* *"I don't have a car. Transit options only."*

Want one of those to carry forward? Ask Runner to remember it, then check **Memory** to make sure it was saved.

A session transcript isn't automatically Memory. Neither is the output from a previous Runner run. The fact has to be written to Personal Memory before another session or run can use it there.

## Put each kind of context in the right place

| What you want to keep                               | Where it belongs                                        |
| --------------------------------------------------- | ------------------------------------------------------- |
| A personal fact or preference                       | **Personal Memory**                                     |
| A standing rule for one Runner                      | That Runner's saved **Prompt**                          |
| Shared background, definitions, or source locations | **Project context**                                     |
| A reusable procedure you choose when to start       | A **Workflow**                                          |
| Live deal, invoice, project, or customer status     | The source app the next run can read                    |
| One run's result                                    | Its session, unless you save the durable part elsewhere |

Memory isn't where every result belongs. Save only the durable part another session or run should use.

## See what Runner remembers

Open **Memory** in the sidebar. Each memory is a document you can read, edit, or delete. Folders can be nested, so you can organize people, preferences, company context, or anything else that needs a home.

If something is wrong, open it and fix it. You can also tell Runner what changed and ask it to update the memory.

You can add one yourself too. Click **New memory**, give it a title and body, done.

***

## Memory keeps itself clean

Memory that grows forever becomes a junk drawer. Runner does its own housekeeping:

**It tidies.** Open **Memory** and click **Organize**. Runner files stray memories into folders in the background. It also runs a weekly cleanup to combine duplicates and keep the structure useful.

**It stays fresh.** Runner periodically sweeps supported connected apps with read-only tools. Those sweeps can update Personal Memory, but they don't change the connected apps.

***

## Turn feedback into memory

Correct the result, then say what should be remembered:

> *"You recommended I drive there, but I don't have a car. Remember to use transit options next time."*

Check **Memory** afterward. If the correction was saved, future sessions can use it without making you repeat yourself.

***

## What's next?

<CardGroup cols={2}>
  <Card title="Projects" icon="folder-open" href="/get-started/projects">
    Keep context that belongs to one Project with that Project.
  </Card>

  <Card title="Runners" icon="person-running" href="/runners/overview">
    See what each Runner gets when a new run starts.
  </Card>
</CardGroup>
