<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Brandon Miller</title>
    <description>The latest articles on DEV Community by Brandon Miller (@millbj92).</description>
    <link>https://dev.to/millbj92</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3872042%2F8a89da11-a084-461f-8fab-213ccef4f41b.jpg</url>
      <title>DEV Community: Brandon Miller</title>
      <link>https://dev.to/millbj92</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/millbj92"/>
    <language>en</language>
    <item>
      <title>EidolonDB – Self-managing memory for AI agents</title>
      <dc:creator>Brandon Miller</dc:creator>
      <pubDate>Fri, 10 Apr 2026 15:21:31 +0000</pubDate>
      <link>https://dev.to/millbj92/eidolondb-self-managing-memory-for-ai-agents-4h9e</link>
      <guid>https://dev.to/millbj92/eidolondb-self-managing-memory-for-ai-agents-4h9e</guid>
      <description>&lt;p&gt;I got tired of my agents making things up in long-horizon or multi-session workflows. So I built a memory layer that refuses to.&lt;/p&gt;

&lt;p&gt;EidolonDB gives agents three memory tiers — short_term, episodic, and semantic — with automatic promotion and decay. You ingest raw conversation text, and an LLM pipeline extracts structured memories, classifies them by tier, scores importance, and deduplicates. Over time, short-term facts either promote to long-term knowledge or expire.&lt;/p&gt;

&lt;p&gt;Key idea: if something isn’t in memory, the system rejects the premise instead of guessing.&lt;/p&gt;

&lt;p&gt;How I validated it&lt;/p&gt;

&lt;p&gt;I built an eval harness with 8 multi-session scenarios:&lt;/p&gt;

&lt;p&gt;project assistant&lt;br&gt;
personal assistant&lt;br&gt;
technical support&lt;br&gt;
preference drift&lt;br&gt;
ambiguous recall&lt;br&gt;
contradictory memory&lt;br&gt;
incomplete recall&lt;br&gt;
temporal retrieval&lt;/p&gt;

&lt;p&gt;Each scenario spans 3 sessions, with a held-out judge scoring:&lt;/p&gt;

&lt;p&gt;recall accuracy&lt;br&gt;
hallucination / false-premise acceptance&lt;br&gt;
Results&lt;br&gt;
No-memory baseline: 0.158&lt;br&gt;
RAG baseline: 0.933&lt;br&gt;
(same rejection prompting; naive RAG ~0.65)&lt;br&gt;
EidolonDB: 1.000&lt;/p&gt;

&lt;p&gt;In particular, EidolonDB consistently rejected false premises that weren’t present in memory.&lt;/p&gt;

&lt;p&gt;What’s available&lt;br&gt;
REST API (self-host or cloud)&lt;br&gt;
Fully self-hostable (Docker + Postgres)&lt;br&gt;
JS SDK (@eidolondb/client) and Python SDK (eidolondb)&lt;br&gt;
Temporal retrieval (“what did we discuss last session?”)&lt;br&gt;
Retrieval feedback loop for lifecycle weighting&lt;/p&gt;

&lt;p&gt;Pricing:&lt;/p&gt;

&lt;p&gt;Free tier&lt;br&gt;
Developer ($19/mo)&lt;br&gt;
Growth ($99/mo)&lt;br&gt;
Links&lt;br&gt;
Site: &lt;a href="https://eidolondb.com" rel="noopener noreferrer"&gt;https://eidolondb.com&lt;/a&gt;&lt;br&gt;
Docs: &lt;a href="https://eidolondb.com/docs" rel="noopener noreferrer"&gt;https://eidolondb.com/docs&lt;/a&gt;&lt;br&gt;
GitHub: &lt;a href="https://github.com/millbj92/eidolondb" rel="noopener noreferrer"&gt;https://github.com/millbj92/eidolondb&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy to answer questions about eval methodology, lifecycle design, or architecture.&lt;/p&gt;

</description>
      <category>agents</category>
      <category>llm</category>
      <category>rag</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
