Memories on start up?

i just got a memory to accept on cursor start up whats goin on with that any more details ?

@bulawow Is that on nightly or regular Cursor? Im not sure why agent would be asking for memories confirmation on startup unless its something thats being worked on.

normal cursor

As Agent would create such memories, its perhaps good that such memories are shown to user for confirmation.

image

im not saying its bad it was just not comunicated that such feature exist and how it exactly works

1 Like

@deanrie is that an intended effect?

I don’t think so. Could you share a screenshot or provide more detailed information?

Well there was not much detail on the bottom left corner it showed me a pop up to either accept or deny to update my memories with a description of the memory then i clicked accept and the memory was saved i cant really recreate it cause i dont really know how i just opened cursor and it appeared and it got added to the memories at the end

Version: 1.2.1 (user setup)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:16:02.610Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

I think this is expected behavior if, for example, you reinstalled Cursor or opened it on another computer. Since the memory is stored in the cloud, it makes sense.

non of that happend

1 Like

[quote=“deanrie, post:9, topic:114604”]the memory is stored in the cloud
[/quote]

Good to know!

OK I was able to reproduce the issue @deanrie

  • Current, incorrect: The memories review screen shows when opening any new window or starting Cursor.
  • Expected: They should be shown when the memories were created instead.

1 Like

Does anybody know how the memory in detail works? I added a chat command that all memories should be written to a markdown file. It is interesting, I gave so many orders to store rules in memory but only a few were in the markdown from the memory. Is there any official documentation? I’m really a little bit annoyed that Cursor ignores rules and the memory usage is a miracle. Does anybody know how that works?

I love the memories, and the first thing when I open Cursor is to load all the rules I created in architecture markdown into the memories. Otherwise, very often they are not used. But in memory, the chance is higher that Cursor respects them and uses them for file creation, modification, and deletion.