Fetching from the wire…
Public story · 2026-08-05 · high
The system sorts dialogue into three memory types and updates only the ones that change, cutting inference cost while beating every baseline tested.
Why now: As of August 5, LeanMem's benchmark numbers are the most direct comparison yet against single-pass memory summarization.
LeanMem sorts every piece of a conversation into one of three memory types, then stores each differently, per a paper posted to arXiv.
Most memory systems for AI agents run everything through one summarization process. That wastes tokens compressing facts that will never change, and loses detail on facts that need to stay exact. LeanMem beat the strongest baseline in every setting tested on LoCoMo and LongMemEval-S, gaining up to 15.1 points. It also ran at the lowest or near-lowest inference token count and latency of the methods compared.
The three types split by how a piece of dialogue behaves over time. Stable facts about a person go into compact profile memory. Things that change as the conversation evolves become temporally structured event memory. Anything that needs to stay traceable to its exact source, like quotes, numbers, or commitments, gets stored as source-grounded record memory.
The part worth taking for production agents is the maintenance rule, not the classification scheme. LeanMem only re-processes event memory when it updates. Profile and record memory get written once and left alone. Most memory implementations re-summarize the whole store on every update cycle, which is where the token cost actually comes from.
The results held across two different models, GPT-4.1-mini and Qwen3-8B, which suggests the gain comes from the architecture and not from either model's quirks.
The paper doesn't say how the routing decision gets made at write time, whether by a classifier, a prompt, or hand-coded rules. That's the detail that decides whether the approach is easy to reproduce.
Each link below shares sources, entities, or timing with this story.
arXiv 2608.11879 benchmarked Mem0, Hindsight and Mastra Observational Memory across conversations up to 400 turns and 665 LoCoMo questions. Cost models built on conversation length miss badly because internal memory behavior dominates. Break-even against just replaying the ful...
July 17, Product Hunt's #1 product was Unabyss for Claude: shared memory across all apps and LLMs, 598 votes. July 18, #1 was ZooData: "the data layer for AI agents," 606 votes. Neither is an application. Both are substrate. (Product Hunt) One launch is noise. Two consecutive...
MemPalace (57,821 stars, v3.6.0) reports 96.6% raw recall@5 on LongMemEval with no LLM required, 98.4% with hybrid v4 on a held-out 450 questions, LoCoMo R@10 rising 60.3% → 88.9%, ConvoMem 92.9%, MemBench 80.3%, while explicitly refusing head-to-head comparison against Mem0,...
Accuracy drops 30–50% well before you hit the documented context limit. Not at the limit. Before it. Cross-model testing across GPT-4.1, the Claude 4 family, Gemini 2.5, and Qwen3 quantified what everyone shipping long-context features has felt and couldn't measure (Glasp). Th...
arXiv 2608.05108 skips the RL-trained attacker models that dominate red teaming and generalize poorly, instead accumulating a strategy library across a sequence of (dataset, target) pairs that transfers to unseen targets with no retraining. AgentDojo: 86.7% ASR against Gemini-...
DeepClaude hit 470 points on Hacker News. It swaps Claude Code's API backend to DeepSeek V4 Pro while preserving the full agent loop: file editing, bash execution, git tooling, the whole workflow. DeepSeek V4 Pro scores 96.4% on LiveCodeBench at a fraction of Anthropic's prici...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.