<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Memory on AiSlackin</title><link>https://aislackin.com/tags/memory/</link><description>Recent content in Memory on AiSlackin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aislackin.com/tags/memory/index.xml" rel="self" type="application/rss+xml"/><item><title>hmem: benchmarking the memory providers fighting for your agent's long-term recall</title><link>https://aislackin.com/posts/2026-08-04-agent-memory-providers/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-08-04-agent-memory-providers/</guid><description>&lt;p&gt;Every agent framework eventually hits the same wall: the context window ends and the conversation forgets. The memory-provider ecosystem that sprang up to fix this is large, fast-moving, and mostly &lt;em&gt;unmeasured&lt;/em&gt; — a lot of READMEs, few numbers. &lt;code&gt;hmem&lt;/code&gt; is my attempt to bring order: a living comparison of fifteen providers compatible with Hermes Agent, from 62K-star mem0 down to single-file SQLite curiosities.&lt;/p&gt;&#10;&lt;p&gt;The part that separates it from a link list is the benchmark discipline. Providers only get scores when a &lt;strong&gt;real measured adapter&lt;/strong&gt; exists — Hindsight and Mnemosyne are listed as &amp;ldquo;not measured&amp;rdquo; precisely because their simulated stubs were excluded. The current controlled run compares BM25 lexical baseline (0.367 correctness) against Hermes built-in memory (0.333) over 30 reviewed scenarios in 10 categories across three isolated runs: 180 result documents, zero failures, machine-readable JSON published alongside the writeup.&lt;/p&gt;</description></item></channel></rss>