SPIN Unprocessed October 23, 2026 ai_technology community
Are we solving LLM memory by remembering more, when the real problem is knowing what to forget?[D]
View original on reddit.comOverview
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 m
SpinGraph analysis pending — check back after processing.
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
More from Reddit r/MachineLearning
View all →- Deepity: a hand-tuned C++/CUDA predictive coding library, beats jpc (JAX) and ngc-learn on MNIST (CPU benchmarks + source inside) [P]
- Practical notes on setting up a GPU kernel-dev environment: CUDA 13's GPU cutoff, async timing pitfalls, profiler counter permissions [P]
- What is the value proposition of "RL environment" companies? [D]
- Papers with Code is now open-source [P]
- How to do method research when I feel I have no guidance on doing it? [D]
- Stenosis detection in coronary angiograms, need recall over precision [D]
Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO