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 108.0ms across 8,687 title embeddings via pgvector HNSW
- Show HN: Lossless-memory – a personal AI memory that never summarizes aru-labs · 59 pts · September 21, 2026 · 59% similar
- Show HN: MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5 pcbmaker20 · 58 pts · August 13, 2026 · 56% similar
- Show HN: A public AI whose memory is shared across all users adjohu · 70 pts · August 16, 2026 · 56% similar
- Choosing the Right AI Agent Memory Strategy: A Decision-Tree Approach eigenBasis · 12 pts · July 11, 2026 · 56% similar
- Agent memory as a file format ingve · 170 pts · August 31, 2026 · 55% 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?