Agent memory
In short
The agent keeps short notes about corrections, preferences and facts it could not have learned from your project, on its own. It shows each one as it saves it; you can undo a turn or delete a note in Settings.
Each new conversation with the agent starts from what your project already holds: the code, your uploaded material, the plans you agreed and the answers you gave in Next Steps. It does not start from something you told the agent earlier. Agent memory closes that gap. When you correct the agent or tell it how you like to work, it saves a short note on its own, and every later conversation on the project starts with that note in view. There is nothing to set up or keep tidy: you teach it by talking to it.
Asking it to remember
You don’t need to. The agent saves a note whenever you correct it or tell it how you like to work. If you want to be sure, say so: “Remember that invoices stay editable until the accountant exports them.” To change a note, tell it what is different now; to drop one, say “forget that” or delete it in Settings.
What it remembers
A note is kept only when nothing else in the project already records it. There are four kinds:
- Correction. You told the agent to stop doing something, or to do it differently, with the reason. “Never edit the contacts table, it is synced from our CRM and edits vanish.”
- Preference. How you like to work. “Show me the plan before any change to the database.”
- Fact. Something true about the project that you cannot see in it. “Invoices stay editable until the accountant exports them each month.”
- Reference. Where something outside the project lives. “The brand colours are in the Figma file we shared.”
The agent does not save what the code already shows, what a plan decided, what an uploaded file says, progress on the task at hand, or anything secret such as a key or a password. If you ask it to save a secret it refuses, and tells you it did not.
Who sees a note
The agent decides this from the kind of note; you don’t choose.
- Just you. Preferences are private to the person they are about. Another member of the project, or an expert working on it, never sees them, and they are never written into the project’s files. Settings shows them with a lock.
- Everyone on the project. Corrections, facts and references belong to the project. They reach every member’s conversations, and the agent can read their full text.
Seeing what it saved
Every time the agent saves or forgets a note, a line appears in the turn’s step box, for example Remembered · Copy is in Dutch. You do not have to go looking for it.
Settings has an Agent memory section that lists every note and when it was saved. A lock marks the notes only you see.
Deleting and undoing
- Delete a note in Settings and the agent stops seeing it in new conversations.
- Undo a turn and the notes that turn saved come back out: a new note is removed, a changed note gets its earlier wording back, and a note the agent forgot returns. Undo reaches only the last turn, and it never brings back a note you deleted.
Notes are not instructions
The agent treats a note as something it wrote down earlier, not as an order. What you ask for now always wins: if you ask for something a note advises against, the agent does what you ask, tells you in a line that it went against the note, and then updates or forgets the note. A note that names a file, a table or a function may be out of date, so the agent checks it is still there before relying on it.
A project keeps at most 200 shared notes. Past that the agent has to forget or merge one before saving another, so the list stays short enough to be read.