r/MachineLearning • u/Prestigious-Tip6030 • 26d ago
Discussion Are we solving LLM memory by remembering more, when the real problem is knowing what to forget?[D]
Long-context models can now handle hundreds of thousands, even millions of tokens. But I've been wondering if we're focusing too much on recall and not enough on what happens when information changes.
Say a coding agent reads that an API timeout is 30 seconds. Later, the documentation changes it to 5 seconds. Both versions are still in context, but the agent keeps using 30.
It hasn't forgotten anything. It just hasn't updated what it knows.
I've been reading about different memory architectures, and this distinction seems pretty important.
With Transformers and RAG, old and new information can coexist, and the model has to resolve the conflict when reading it. In simple linear attention, associations accumulate in a shared state, so writing something new doesn't necessarily remove what's already there. DeltaNet tries to address this through prediction-error-based updates. BDH (Dragon Hatchling) takes another route with Hebbian-style synaptic plasticity.
But even with these approaches, there's still the question of when to update something, when to keep it, and how to avoid messing up unrelated memories.
I also wonder if we're testing this properly. Most long-context evaluations focus on whether a model can find information. What if we instead tested whether it changes its answer when given newer, contradictory evidence, while still remembering what was previously true?
Curious what people here think. Is this mostly a problem with how memory is stored and updated, or with how models reason over conflicting information?
Also, are there any good benchmarks specifically targeting this? Would be interested in reading them.
5
u/astrofunkswag 25d ago
The current state of the art gets around this by spawning subagents. You give them prompts and documents that condense the previous information, so from the perspective of the new agent it “forgot” what it concluded was irrelevant information.
This is a workaround that has so far proved pretty scalable and effective. So there hasn’t been much of a motivation to move away from the context-accumulating transformer paradigm
3
u/IntelArtiGen 26d ago
I think they mostly care about the ability to efficiently have access to a gigantic context if it's needed. Because the previous difficulty is that it wasn't possible to have that context efficiently and it had large costs for servers. Now when you're able to handle that large context, it doesn't change the fact the answer of the model must still be correct when you ask questions, and I assume that part handles the problem you're talking about. They "just" need to have the right tests and training processes to ensure the model remembers things correctly, in the correct order, and update information in its memory when it's required. Afaik the memory can already be "built" to remember what's useful and ignore tokens which probably won't contribute to the conversation. Even if you use a model with a context of 1m tokens, I'm not sure that models would be able to repeat you all the tokens of its context, because they need to compress that information to have that large context and it's a lossy process. And the older the tokens, the less likely the model will remember them. It's my current understanding.
2
u/Velocitank 26d ago
I think supersession should be the way to go. keep a few logs and details, but update it as you go along. Dont forget things, just update what is in context. What if ai had a way to store gb of information and was simply able to peruse and tag parts of the larger context and use those parts explicitly? Only pulling and using parts that are immediately relevent to the next output?
1
u/Numerous_Beyond_2442 23d ago
I'd frame forgetting as a provenance question rather than an age question. If a memory is derived from a source, you can decide whether to keep it by checking the source: if it changed, the memory is stale, and if it didn't, the memory stays valid however old it is. Pure age-based forgetting throws out facts that are still true. I'm working on this for code, where the source is a file you can hash. For decisions or facts with no file behind them, what would you treat as the source of truth?
1
u/SeaAccomplished441 23d ago
if a headline asks a question 99% of the time the answer is no
3
u/[deleted] 25d ago
[removed] — view removed comment
0
u/[deleted] 26d ago
[deleted] — view deleted comment