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

# Devin Memory and Dreaming

> Devin Memory saves your preferences, corrections, and project lessons as notes that carry across sessions, and Dreaming keeps those notes organized.

## What is Memory?

Memory lets Devin carry what it learns from working with you into future sessions: your preferences, corrections you've made, and lessons about your projects and environment. Devin saves these on its own as you work, so you don't have to stop and write them down.

Memory is **personal to you** within each organization. It is not shared with your teammates or your organization.

## How it works

Your memories live in a **memory drive**: a persistent Git repository of Markdown notes.

```text theme={null}
memory/
  MEMORY.md          ← general preferences + an index of the other files
  my-app/
    testing.md
  tools/
    datadog.md
```

1. **Load.** Each session gets its own checkout of the drive and receives `MEMORY.md` as context. Devin searches and reads the other notes only when the task needs them.

2. **Learn.** When you correct Devin, explain a preference, or it works out something reusable, Devin edits the relevant note. Each entry is a one-line bullet that links back to the session where it was learned:

   ```markdown theme={null}
   - Use bun, not npm; the lockfile is bun.lock [source: https://app.devin.ai/sessions/abc123; added: 2026-10-05]
   ```

3. **Save.** Devin commits the edit, merges changes from your other sessions, and saves the result to the drive. An **Updated memory** card in the session shows what changed. Parallel sessions can write to the same drive: a stale write is rejected and retried, and conflicting edits are resolved rather than overwritten.

New memories apply to future sessions, not the one that wrote them.

### What Devin remembers

| Saved | Not saved |
| - | - |
| Preferences for how you want Devin to work and communicate | Summaries of sessions |
| Corrections, with the rule to follow next time | Task state, such as PR numbers or statuses |
| Decisions and the reasons you gave | Anything cheap to rediscover |
| Gotchas about your repos and environment | Secrets and credentials |

Sessions started by [automations](/product-guides/automations) don't read or write your memory.

## Dreaming

Dreaming is a background session that runs about once a day when you've been using Devin. It reviews your recent sessions alongside your existing memory and:

* Consolidates overlapping notes
* Removes transient details and stale notes that no session has used
* Adds useful lessons that weren't captured during the original work
* Reorganizes notes and the `MEMORY.md` index so the right context is easier to find

Source links and explicit preferences are preserved. Your first dream seeds memory from your recent sessions.

## View and manage memory

Open [**Customize → Memory**](https://app.devin.ai/customize?tab=memory) to browse your memory files and see recent dreaming sessions with what each one changed.

* **Change or remove a memory**: Memory files are read-only in the app. Ask Devin in a session, for example "forget that I prefer npm" or "remember that staging deploys need approval."
* **Turn memory off**: On the Memory tab, open the **⋯** menu and select **Turn off personal memory**. Devin stops reading and writing memory; your existing notes are kept if you turn it back on.

## Admin controls

Memory is on by default. Admins can change that at two levels:

| Level | Where | Options |
| - | - | - |
| **Organization** | **Settings → Devin → Sessions → Memory** | A switch that turns Memory on or off for every member of the organization. Requires permission to manage organization settings. |
| **Enterprise** | **Enterprise settings → Devin → Sessions → Memory** | **Default on**: on everywhere, and each organization can turn it off. **Always on**: on for every organization. **Always off**: off for every organization. Requires permission to manage enterprise settings. |

With **Always on** or **Always off**, the organization switch is locked. When Memory is on, each member can still [turn off their own memory](#view-and-manage-memory).

When Memory is off for an organization, Devin doesn't read or write memory in that organization's sessions, dreaming doesn't run, and the Memory tab is hidden. Existing notes are not deleted.

## Memory vs. Skills

| | Memory | [Skills](/product-guides/skills) |
| - | - | - |
| **What it holds** | What Devin learns while working with you | A repeatable procedure, such as how to test or deploy |
| **Who writes it** | Devin, automatically, refined by dreaming | You or your team, deliberately |
| **Scope** | Personal | Repository, personal, organization, or enterprise |

They work together: a skill provides the procedure, and memory supplies the context for applying it to your work.

## Open standard

Devin's memory is built on [Agent Memory Repo](https://github.com/AgentMemoryRepo/agentmemoryrepo), an open spec that treats agent memory as a Git repository with a `MEMORY.md` entry point, one-line entries with `[source: …; added: …]` metadata, and `[[path]]` links between files. You can use the same format in your own agents.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.