What happened
Memories was the feature that let Cursor remember things from your chats and use them in the next one. After the update to version 2.1, users found their memories gone. On the Cursor forum, a staff member wrote on November 25, 2025: “The Memories feature was intentionally removed starting from version 2.1.x.”
So it was not a bug or an outage. Cursor’s current docs on rules do not mention Memories. Explicit, lasting instructions now go into rules, AGENTS.md, and skills. Separately, Projects retain context that agents learn, and Automations keep memory across their runs.
Save your memories first
Cursor’s November 2025 migration advice was to run Export memories and move the exported .mdc content into rules. Some users on the forum report that the command is missing; check whether your installed version still offers it, and ask Cursor support if it does not.
- Open the command palette (Cmd+Shift+P on a Mac, Ctrl+Shift+P on Windows).
- Type “Export memories” and run the command, if it is available. Your memories are saved to an
.mdcfile. - Read the file. Delete what is outdated or too personal to share.
- Put what applies only to you in your User Rules (Customize > Rules).
- Put what applies to the project in a rule in
.cursor/rules/and commit it, so your teammates have it too.
Rolling back to version 2.0.77 brings the memories back, according to users, but Cursor staff called that a stopgap: older versions will lose support. Exporting is the way forward.
What to use instead of Memories
| What you wanted remembered | Where it belongs now |
|---|---|
| Your own preferences (language, style, how you want answers) | User Rules |
| Agreements about this project (structure, conventions, things to avoid) | Project Rules in .cursor/rules/*.mdc or AGENTS.md |
| Agreements for the whole team | Team Rules, on a Team or Enterprise plan |
| A procedure with steps or scripts | A skill in .cursor/skills/ |
How to set up those rules and pick a type is covered in How do you use Cursor rules.
The common mistake: rules are not memories
Turning memories into rules gives you your context back, but not the remembering itself. The difference is who writes. Cursor filled Memories from your chats. You write and maintain rules yourself. A correction in one chat does not automatically become an instruction for every future chat.
That is not only a loss. A rule sits in a file you can read, review, and commit. You see exactly what the agent relies on, and your teammates get the same. Memories were personal and invisible to the rest of the team.
How to keep memory across sessions now
- Make corrections stick. When you correct the agent twice on the same thing, turn it into a rule right away.
- Write where it travels. Prefer Project Rules or
AGENTS.mdin the repository over User Rules, so the context reaches every machine and every teammate. - Keep it short. Cursor recommends rules under 500 lines. Split big ones and let globs or a clear description decide when they load.
- Turn procedures into skills. A skill’s full instructions load when needed; the rest of the time only its name and description are visible to the agent.
What this means for a team
Memories lived with one user. What your Cursor had learned, your teammate’s Cursor did not know. The removal makes that visible: what the team needs to know belongs in a shared place. Have every developer who still has the export command export their memories, pull out the agreements that hold for everyone, and put those in Project Rules or Team Rules. How to spread that across the team: How do you share context and team rules in Cursor.
Where Bombos fits
Bombos keeps what Memories used to keep, but for the whole team and for every AI tool: it is a plugin that gives Cursor, Claude Code, ChatGPT, Copilot, and other tools one shared memory with team knowledge, rules it learns from corrections, and what already sits in email, documents, and repos. You can see what each answer rests on, in the cloud or on your own server. One developer can try it first with their own agents.
Related questions
Can I get Memories back by downgrading?
Users reported that rolling back to version 2.0.77 brings the memories back. Cursor staff called that temporary, since older versions will lose support, and in November 2025 recommended exporting instead.
Where do exported memories go?
Into an .mdc file. You then add the content to your User Rules or to Project Rules in .cursor/rules.
Does Cursor still remember anything between sessions?
Rules and AGENTS.md provide explicit instructions that you write yourself. Cursor Automations also have memory across runs, and Projects retain context that agents learn while they work.
