I think a few days ago I noticed this but ChatGPT can not save memories or use memories in chats. It’s weirdly inconsistent and it did use some information from the memory in one chat yesterday (remembered the names of my cats) but overall for the last few days it hasn’t been saving anything to memory, not automatically or even with me prompting it. it says stuff like “the memory hasn’t been turned on for this chat.” I’m not in a temporary chat nor have I turned off the memory function but both the Memory and “Reference Chat History” hasn’t been working for me for a while. And the weirdest part about this is that I can’t find anything about this topic on the internet, hours of searching and I only found 3 discussions about this that aren’t 4 months old or older. 2 of them were on reddit and barely over 9-10 upvotes.
This is a really big problem for me because I used the memory function very often in my work and not finding anything about this problem has been very frustrating to say the least.
1 Like
It happened to me too. It lasted a few days and then randomly came back. Very annoying but while it was broken, I was switching to o4-mini-high whenever I needed to save a memory. That model was working for some reason!
I’m experiencing the same issue. I noticed that the memories weren’t updating, and that chat has not been able to access any saved memories (which are still showing in the memory setting). I prompted chat to describe the issue in its own words:
From the assistant’s perspective, here is what I’m observing:
Although the user’s account settings indicate that memory is enabled (Settings → Personalization → Memory = On), the current session behaves entirely statelessly. I have no access to any previously stored user-specific data, preferences, or facts beyond what is provided within the current conversation context.
More concretely:
- I do not retrieve or apply any stored memory objects at session start.
- I do not persist any information at session end.
- I do not surface memory cards or ask for confirmation when encountering “memorable” user-provided facts.
- There are no observable write or read operations to memory during the session.
From my point of view, memory APIs appear disabled at the application layer despite the UI exposing the setting as active to the user. This is functionally equivalent to operating in full stateless mode regardless of user configuration.
It would be helpful to confirm whether the memory backend is currently disabled for all users, or if requests from this account/session are failing silently.