Show HN: I evaluated file, vector, graph and RL based memory frameworks
pinglin
13 points
1 comment
August 15, 2026
Related Discussions
Found 5 related stories in 156.7ms across 13,334 title embeddings via pgvector HNSW
- Show HN: MemorySync – Memory for AI Agents mohd_rafay · 22 pts · October 13, 2026 · 64% similar
- Show HN: Graphicle, a Rust port of Graphify with memory for coding agents KarLexAI · 44 pts · October 14, 2026 · 61% similar
- Show HN: Interactive notes on RLHF, attention, LoRA and LLM evals laxmena · 40 pts · November 03, 2026 · 59% similar
- Show HN: Lossless-memory – a personal AI memory that never summarizes aru-labs · 59 pts · September 21, 2026 · 59% similar
- The Components of Agent Memory geoffbp · 155 pts · November 07, 2026 · 58% similar
Discussion Highlights (1 comments)
neiltonrocha
I’ve been running into this while adding memory to agents we use across the companies I’m building. In the paper, structured memory scored 73.6% vs. 44.9% for files. But on abstention, it went the other way: 77.8% vs. 88.9%. That’s also where I’m struggling most today. Retrieving context is one thing. Knowing what is still valid when information gets old or conflicts is harder. I’ve been talking to other teams working on this and haven’t seen an approach that handles it really well yet. How are you dealing with this in production?