<?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: Filippo Pilotta</title>
    <description>The latest articles on DEV Community by Filippo Pilotta (@filippopilo).</description>
    <link>https://dev.to/filippopilo</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4089885%2F81c0506b-fea9-41d9-8cef-61e828e8229d.jpg</url>
      <title>DEV Community: Filippo Pilotta</title>
      <link>https://dev.to/filippopilo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/filippopilo"/>
    <language>en</language>
    <item>
      <title>Why is everyone so skeptical of AI memory tools? Fair question. Here are real answers.</title>
      <dc:creator>Filippo Pilotta</dc:creator>
      <pubDate>Sat, 22 Aug 2026 15:17:33 +0000</pubDate>
      <link>https://dev.to/filippopilo/why-is-everyone-so-skeptical-of-ai-memory-tools-fair-question-here-are-real-answers-4g1p</link>
      <guid>https://dev.to/filippopilo/why-is-everyone-so-skeptical-of-ai-memory-tools-fair-question-here-are-real-answers-4g1p</guid>
      <description>&lt;p&gt;Last week I presented Cortex — a semantic memory for AI assistants I've been building for two years — on Reddit. The response was brutal: &lt;em&gt;"Obsidian works fine."&lt;/em&gt; &lt;em&gt;"A text file is enough."&lt;/em&gt; &lt;em&gt;"Thanks for inventing RAG for the millionth time."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Instead of deleting the post, I answered everyone. And I realized the skepticism isn't stupidity — it's precious information. This article is the structured version of those answers, including the uncomfortable ones.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Transparency note: I build memory tools for AIs, and I use AIs daily to multiply what one person working alone can do — including help writing this article. The architecture, the patent filing, the benchmarks and two years of late nights are mine.)&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the distrust is justified
&lt;/h2&gt;

&lt;p&gt;Three reasons, all well founded.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Saturation.&lt;/strong&gt; A new "memory tool" ships every week. Almost all do the same thing: save conversations into a vector database, fish them back out. Distrust is an immune response, and it works.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The promises.&lt;/strong&gt; "Infinite memory," "your second brain," "never forgets anything." Slogans nobody can measure, so nobody believes them anymore.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The black boxes.&lt;/strong&gt; You hand your data to a system that won't tell you what it saves, why, or what it will answer tomorrow. An AI that doesn't remember is a tool. An AI that remembers &lt;em&gt;badly&lt;/em&gt; — picking at random between contradictory memories — is worse than useless.&lt;/p&gt;

&lt;p&gt;Cortex was born from exactly these three problems. Not "how do I save everything?" but: &lt;strong&gt;how do I decide what deserves to be remembered? And what happens when memories contradict each other?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  "Why not Obsidian?"
&lt;/h2&gt;

&lt;p&gt;Because they solve two different problems that look like the same problem.&lt;/p&gt;

&lt;p&gt;Obsidian is memory &lt;strong&gt;for you, maintained by you&lt;/strong&gt;: you write, organize, link. It's excellent at that. Cortex is memory &lt;strong&gt;for the AI, maintained by the system&lt;/strong&gt;. Four concrete differences:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Who decides what gets in.&lt;/strong&gt; In a vault, everything you write gets stored. In Cortex, every write passes a quality gate that in production rejects ~80% of proposals as redundant. A vault has no concept of "this note doesn't deserve to exist."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contradictions.&lt;/strong&gt; In a vault, the March note and today's note coexist in silence. Cortex detects and tracks them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where it works.&lt;/strong&gt; A vault lives on your desktop. Cortex is identical from the web, your phone, Claude and ChatGPT.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Maintenance.&lt;/strong&gt; A useful vault is a garden that needs pruning. Cortex prunes itself.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The honest concession, same one I made on Reddit: if you're disciplined, desktop-only and single-model, a good vault covers most of the need. For free. &lt;strong&gt;Obsidian archives documents. Cortex governs memories.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  "A memory.md file is enough"
&lt;/h2&gt;

&lt;p&gt;At first, it is — we've all been there. Then it grows: no deduplication, no contradiction detection, and it gets pasted whole into every conversation's context — and context costs money. A memory file is a sticky note: perfect as long as the project fits on a sticky note.&lt;/p&gt;

&lt;h2&gt;
  
  
  "What about Mem0, Zep, Graphiti?"
&lt;/h2&gt;

&lt;p&gt;That's the right comparison class, and they're solid projects. If you can self-host and want full control, use them. The differences I claim: Cortex is hosted with zero setup (works from your phone, no infrastructure), the write-time quality gate is the core of the design rather than an option, and conflicts are first-class objects.&lt;/p&gt;

&lt;h2&gt;
  
  
  "It's just RAG with marketing"
&lt;/h2&gt;

&lt;p&gt;The retrieval side &lt;em&gt;is&lt;/em&gt; RAG, no argument: embeddings, semantic search, context handed to the model. But classic RAG is a read-only pipeline over an archive someone else has to keep clean: it indexes everything, and answer quality depends entirely on archive quality.&lt;/p&gt;

&lt;p&gt;Cortex steps in where RAG stops:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Writing is governed&lt;/strong&gt; — novelty filter, facts extracted as typed claims, deduplication at write time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory has a lifecycle&lt;/strong&gt; — consolidation over time, updates linked to the record they supersede, a database that refines itself instead of bloating.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An epistemic layer&lt;/strong&gt; — tracked contradictions, a coherence score, citable sources.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;RAG retrieves from an archive. Cortex curates the archive. If that's still "just RAG" to you, fine: it's RAG with a bouncer.&lt;/p&gt;

&lt;h2&gt;
  
  
  The best question Reddit asked: "When two memories contradict each other, who decides which one wins?"
&lt;/h2&gt;

&lt;p&gt;The system doesn't choose in silence — that's a design decision. Search returns &lt;em&gt;both&lt;/em&gt; memories, flagged with a warning, reliability scores and dates. The synthesis layer prefers the most recent but declares that the older one has been superseded, citing both. And the conflict remains an object with a status: open or resolved. You can list them; you can resolve them yourself.&lt;/p&gt;

&lt;p&gt;One rule: &lt;strong&gt;the system may have an opinion about who wins, but it never has the right to hide the disagreement.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The uncomfortable number
&lt;/h2&gt;

&lt;p&gt;On the LoCoMo benchmark (1,986 questions over long conversations), Cortex scores ~69% with the filter off and ~56% with the filter on. We published both numbers ourselves.&lt;/p&gt;

&lt;p&gt;Why publish the worse one? Because the filter isn't free: 13 points is the &lt;em&gt;measured price&lt;/em&gt; of a memory that rejects 80% of writes instead of accumulating everything. LoCoMo rewards total recall of conversational trivia; a memory that filters trivia loses points on trivia questions, by design. Meanwhile adversarial questions stay at 95%, and storage drops by 30%.&lt;/p&gt;

&lt;p&gt;Filter off tells you the retrieval engine is at state-of-the-art level. Filter on is a different objective: governed memory, not maximum recall. Choose what you need — but choose it with the numbers in front of you, not the slogans.&lt;/p&gt;

&lt;h2&gt;
  
  
  The quick ones
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Open source?&lt;/strong&gt; No — the engine is closed, covered by a patent application filed May 2026. The connector, docs and examples are on &lt;a href="https://github.com/FilippoPilo/cortex-connector" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;, and Cortex is on the official MCP registry. I'd rather say it to your face than dance around it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need an account to try it?&lt;/strong&gt; No: add the remote MCP connector to your client and the trial space creates itself on first sign-in. 30 days, no credit card.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why pay when open source is free?&lt;/strong&gt; If you can self-host, genuinely, do it. Cortex is for those who can't or don't want to.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Who's behind it?&lt;/strong&gt; One person: independent researcher, founder of SKYNETLAB, Bergamo, Italy. Two years of work, no team, no funding.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I actually learned from getting roasted
&lt;/h2&gt;

&lt;p&gt;Skepticism toward AI memory tools is rational — the category earned it. The only sane response is verifiability: publish the write path, publish &lt;em&gt;all&lt;/em&gt; the numbers (including the ones that hurt), and keep disagreements visible instead of swallowing them.&lt;/p&gt;

&lt;p&gt;Every answer here is written down, with the numbers, on the &lt;a href="https://www.skynetlab-cortex.com/faq" rel="noopener noreferrer"&gt;FAQ page&lt;/a&gt;. Brutal feedback welcome — it's the most useful gift you can give. I learned that this very week.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>memory</category>
      <category>mcp</category>
      <category>llm</category>
    </item>
  </channel>
</rss>
