I kept wondering why the agent could not remember things I had told it to remember, which used to work fine but now does not. When I asked the agent, here’s the response it said it tried to make the call to memory but it failed. So you might wanna look at that. Either it’s maybe a bug or you’re deprecating that feature. But either way, here is the transcript.
Checking available tools for memory-related functionality:
I don’t have access to any memory tools. When I tried update_memory earlier, I got:
Error calling tool: Tool update_memory not found. Available tools: [“codebase_search”,“run_terminal_cmd”,“grep”,…]
Error calling tool: Tool update_memory not found. Available tools: [“codebase_search”,“run_terminal_cmd”,“grep”,…]
My available tools don’t include any memory-related functions, even though Memories is enabled in your Cursor settings. This suggests the memory functionality may not be exposed to the agent in this environment, or it’s handled differently (e.g., automatically by the system rather than via a tool).
I can see the existing memories you mentioned (navigation patterns, SqlProp references, rest_model_docs.md), which are provided in my context, but I can’t create new ones programmatically.
Steps to Reproduce
To reproduce this bug, you just have to ask the agent to remember something and commit it to memory (long-term memory), and it can’t. Or, you can check your memories and see that it’s not there, and then ask the agent about it. That’s the dialogue that I included.
Expected Behavior
Expected behavior is that the agent could add memories into the project memories.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
After upgrading to version 2.1.17, there is no longer any memories in the cursor settings. So I went back and downgraded back to 2.0.77 and migrated my memories, the ones that I still wanted, to rules. So I would suggest that anyone that is using their memories, they should probably migrate them to rules because you lose the ability to remove or update them, and the AI can’t do it either. It also couldn’t find them. So before you update, you might want to migrate your memories.
This is outragous. memories persisstence has been broken for me for months now and instead of fixing it they remove the feature altogether. job well done team.
Honestly, I enjoyed them as well but it did open my eyes to cleaner solutions that assist more in consistent development.
Running “openspec init” and pasting the one prompt it gave me into cursor “auto” created a wonderful project.md file which I also integrated my notes into. You might consider this as an improved alternative that requires no new keys or cost. It integrates seamlessly into cursor.
I also downloaded 2.0.77 to try recovering my lost memory. Did you replace the newer version with 2.0.77 and run it directly? I launched the older build from the package, so I am not sure if that is why it is not working for me.
Yes, I had already downloaded 2.0.77 and installed it right over the current version I had. Before I did that I set the Beta → Update Access to “default” so it wouldn’t download the newer version that wasn’t working. With 2.0.77 I could see my memories in the settings page and so could the agent when I asked it about them. I asked the agent to take those memories and create a file with them and later had it also incorporate those memories into my current markdown files for the project.
