Agent memory worked better as a statement graph than as a bigger context window
chrislally · reddit · 2026-07-26
The author found that agent memory kept failing when they tried to make it work by stuffing more context into the window or searching harder over history.
They switched to a statement graph model with typed entities, relationships, and statements about statements, so each fact can carry provenance, validity windows, and supersession history. The post lays out several lessons:
- framework memory assumptions break under real-world identity conflicts and temporal validity
- names should be treated as labels, not IDs
- temporal history should be appended, not overwritten
- conflicting claims should remain visible until a policy or human resolves them
- resolution depends on trust rules, so the believed result should be recorded too
The remaining open problem is context assembly: how to pick the right bounded slice of the graph during execution.
Related event: Andrew Ng Advocates Graph-Based Memory for AI Agents(2 posts)→
More from coding & agent
- HeyGen + Canva MCP turns slide speaker notes into an avatar presentation video — HeyGen · 2026-10-27
- 10 practical ways to run Astra computer use on Premiere Pro for video editing — beechinour · 2026-10-27
- Dev ships a delightful free shadcn UI for agent run and tool-call traces — round · 2026-10-27
- Phil Schmid launches Gemini API CLI: a stateless multimodal tool belt for your existing coding agent — _philschmid · 2026-10-27
- Musk hails Grok Bot as 'incredibly competent chief of staff' as user automates inbox triage — elonmusk · 2026-10-27
- shadcn's /improve skill paired with Grok on SuperGrok Heavy for plowing through issues — shadcn · 2026-10-27