# Memory

> How the KazoCode agent remembers your preferences, corrections and project decisions across conversations, and how to add, edit and remove memories.

Memory lets the agent carry what it learns from one conversation to the next: your preferences, corrections you've made, and decisions about the project that aren't written down anywhere in the code.

## What gets remembered

The agent saves a memory when you correct it, state a preference, or confirm an approach that wasn't obvious. Each memory has a type:

| Type | Example |
| --- | --- |
| **user** | "Prefers small commits with tests in the same commit." |
| **feedback** | "Don't add code comments unless they're needed. Why: the team reads the code, not the comments." |
| **project** | "The billing rewrite ships on March 3; don't touch `billing/` until then." |
| **reference** | "Bugs are tracked in the Platform board on Linear." |

It deliberately doesn't save what the repository already says, such as code structure, file paths or Git history, and it checks that a remembered file or function still exists before relying on it.

## Scopes

- **User** memories follow you into every project.
- **Project** memories apply only to the current project.

## Managing memories

- `/remember <note>` saves a note yourself, for example `/remember the staging database is read-only`.
- `/memory` lists memories and instruction files and opens one to edit.
- **Settings › Rules & Memories** shows everything the agent remembers about you and the project; edit or delete any of it there.

When a memory turns out to be wrong, the agent updates or removes it rather than keeping a contradiction.

> [!NOTE]
> Memory is for facts that change how the agent should work. Project conventions everyone should follow belong in a [`KAZO.md` file](https://kazocode.app/docs/customize/instructions.md), where your team can read and review them.
