$ ls topics/memory/
memory/
how agents store, retrieve, and lose context
· memoryJul 2026How I built the workers that keep a structured memory graph cleanRecallatron uses entity graphs and episodic timelines instead of vector embeddings. Four nightly workers handle resolution, deduplication, profiling, and auto-confirmation. The graph stays usable without a human doing maintenance.10 min· memoryJun 2026Give the model the tools, not the contextThe naive way to give an AI assistant memory is to inject recent turns into every prompt, and it hits a wall fast. The better design hands the model a set of tools and lets it decide what to retrieve, what to compress, and what is worth writing down at all.8 min· memoryJun 2026One call. The real prerequisite.Rheo's session boot went from four memory calls to one. The call count was never the achievement; the store's shape was.6 min· memoryJun 2026Memory is easy. Retrieval is hard.We assumed memory would be the hard part of building Rheo, our Claude assistant. It wasn't; the bottleneck was retrieval, not storage.6 min