<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Curator Blog</title><description>Notes from the team building Curator, evolutionary memory for AI agents.</description><link>https://blog.curatormcp.com/</link><language>en-us</language><item><title>An Encrypted Memory Should Survive a Reinstall</title><link>https://blog.curatormcp.com/an-encrypted-memory-should-survive-a-reinstall/</link><guid isPermaLink="true">https://blog.curatormcp.com/an-encrypted-memory-should-survive-a-reinstall/</guid><description>Encryption at rest has a failure mode nobody advertises: lose the key and a healthy store is noise. Preparing Curator&apos;s first public build meant making sure a new machine, a reinstall, or an upgrade never costs you your memory.</description><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>memory</category><category>safety</category><category>reliability</category><author>Curator</author></item><item><title>Only Settled Decisions Carry Forward</title><link>https://blog.curatormcp.com/only-settled-decisions-carry-forward/</link><guid isPermaLink="true">https://blog.curatormcp.com/only-settled-decisions-carry-forward/</guid><description>When Curator opens a project it can bring in defaults you hold elsewhere. That is the most useful thing it does and the easiest to get wrong. It now offers only positions that have held up, that you made, and that bear on the project in front of you.</description><pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate><category>memory</category><category>resume-diff</category><category>integrity</category><author>Curator</author></item><item><title>When Every Agent Writes at Once</title><link>https://blog.curatormcp.com/when-every-agent-writes-at-once/</link><guid isPermaLink="true">https://blog.curatormcp.com/when-every-agent-writes-at-once/</guid><description>Run enough agent sessions against one memory and the hard part stops being recall. It becomes making sure every save lands. Curator got a round of hardening for exactly that kind of load.</description><pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate><category>memory</category><category>reliability</category><author>Curator</author></item><item><title>Memory Earns Its Place as the Stack Grows</title><link>https://blog.curatormcp.com/memory-earns-its-place-as-the-stack-grows/</link><guid isPermaLink="true">https://blog.curatormcp.com/memory-earns-its-place-as-the-stack-grows/</guid><description>As the rest of the stack gets better at producing verified, current context and proving tools correct, a persistent memory layer is worth more, not less. Its job is to keep what was learned so the next session does not start from zero.</description><pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate><category>ecosystem</category><category>memory</category><author>Curator</author></item><item><title>Your Session Survives a Compaction</title><link>https://blog.curatormcp.com/your-session-survives-a-compaction/</link><guid isPermaLink="true">https://blog.curatormcp.com/your-session-survives-a-compaction/</guid><description>Long agent sessions get compacted, and the summary usually throws away what you were in the middle of. Curator now puts the working thread back the moment a session compacts, so the agent keeps its footing instead of going blank.</description><pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate><category>memory</category><category>sessions</category><author>Curator</author></item><item><title>The brain got an upgrade. It had to win a bake-off first.</title><link>https://blog.curatormcp.com/win-the-bake-off-first/</link><guid isPermaLink="true">https://blog.curatormcp.com/win-the-bake-off-first/</guid><description>Curator&apos;s write-time understanding and its recall retrieval both got stronger this sprint. Neither swapped in on reputation. Each replacement had to beat the model already in place, head to head, on a real store, before it shipped.</description><pubDate>Tue, 25 Aug 2026 00:00:00 GMT</pubDate><category>memory</category><category>local-llm</category><category>benchmark</category><author>Curator</author></item><item><title>The features we ship turned off</title><link>https://blog.curatormcp.com/when-the-numbers-say-no/</link><guid isPermaLink="true">https://blog.curatormcp.com/when-the-numbers-say-no/</guid><description>A memory layer stuffed with clever mechanisms sounds better than one that runs only what it can prove. Curator ships the clever ideas disabled when measurement refutes them, treats a revert as data, and keeps live only the parts that earned their place.</description><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><category>memory</category><category>reliability</category><category>evals</category><author>Curator</author></item><item><title>A wall of text is not an answer</title><link>https://blog.curatormcp.com/a-wall-of-text-is-not-an-answer/</link><guid isPermaLink="true">https://blog.curatormcp.com/a-wall-of-text-is-not-an-answer/</guid><description>Retrieval scores are easy to game: return more, and it looks like a hit. Curator grades its recall the way a user actually judges it, so a confident wrong answer scores worse than an honest blank, and a paragraph of near misses does not count as getting it right.</description><pubDate>Thu, 06 Aug 2026 00:00:00 GMT</pubDate><category>memory</category><category>recall</category><category>quality</category><author>Curator</author></item><item><title>A memory you can measure beats one you just trust</title><link>https://blog.curatormcp.com/a-memory-you-can-measure/</link><guid isPermaLink="true">https://blog.curatormcp.com/a-memory-you-can-measure/</guid><description>Most AI memory asks you to trust that recall is good. Curator benchmarks its own memory on a frozen copy of a real store, with the test and the result that would prove it wrong both written down before the run. Quality you can measure, not quality you assert.</description><pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate><category>memory</category><category>evals</category><category>benchmark</category><author>Curator</author></item><item><title>The Amnesia Bottleneck</title><link>https://blog.curatormcp.com/the-amnesia-bottleneck/</link><guid isPermaLink="true">https://blog.curatormcp.com/the-amnesia-bottleneck/</guid><description>Scaling AI engineering breaks on four bottlenecks, and the quiet one is amnesia. Curator removes it with memory that applies what changed since you last touched a project, so agents resume with your current judgment instead of relearning your old mistakes.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><category>ecosystem</category><category>memory</category><author>Curator</author></item><item><title>Curator Can Stop the Edit Before It Breaks Your Code</title><link>https://blog.curatormcp.com/stop-the-edit-before-it-breaks/</link><guid isPermaLink="true">https://blog.curatormcp.com/stop-the-edit-before-it-breaks/</guid><description>Most memory only remembers a decision and hopes the agent reads it. Curator puts the recorded decision in front of the agent at the moment of the edit, and in enforce mode hard-blocks the change outright until the decision is honored or superseded.</description><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><category>memory</category><category>enforcement</category><category>guardrails</category><author>Curator</author></item><item><title>Overnight, Done Right</title><link>https://blog.curatormcp.com/overnight-done-right/</link><guid isPermaLink="true">https://blog.curatormcp.com/overnight-done-right/</guid><description>Bulk overnight catch-up can bury the memories that matter. This release ships the guardrail: docs and git history by default, raw transcripts behind an explicit opt-in, and every cleanup reversible because nothing is ever deleted.</description><pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate><category>memory</category><category>consolidation</category><category>safety</category><author>Curator</author></item><item><title>Why AI Memory Gets Worse the More You Feed It</title><link>https://blog.curatormcp.com/why-ai-memory-gets-worse/</link><guid isPermaLink="true">https://blog.curatormcp.com/why-ai-memory-gets-worse/</guid><description>Teams assume more memory is better, so they import everything, and recall gets worse. Volume buries signal. A memory layer has to rank by durability, ingest selectively, and demote reversibly to keep getting sharper as it grows.</description><pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate><category>memory</category><category>recall</category><category>rag</category><author>Curator</author></item><item><title>Seeded from your git history</title><link>https://blog.curatormcp.com/seeded-from-your-git-history/</link><guid isPermaLink="true">https://blog.curatormcp.com/seeded-from-your-git-history/</guid><description>A fresh memory knows nothing about a project that already has years of history. Curator can backfill from your git log and docs overnight, so it starts useful instead of empty.</description><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><category>memory</category><category>onboarding</category><author>Curator</author></item><item><title>Memory that improves overnight</title><link>https://blog.curatormcp.com/memory-that-improves-overnight/</link><guid isPermaLink="true">https://blog.curatormcp.com/memory-that-improves-overnight/</guid><description>Left alone, notes pile up and rot. Curator does the opposite: each night it consolidates what it has learned, so the next day it recalls better instead of noisier.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><category>memory</category><category>consolidation</category><author>Curator</author></item><item><title>Good memory knows when to refuse</title><link>https://blog.curatormcp.com/good-memory-knows-when-to-refuse/</link><guid isPermaLink="true">https://blog.curatormcp.com/good-memory-knows-when-to-refuse/</guid><description>Most memory layers degrade quietly: they&apos;ll store noise and rank it next to truth. Curator refuses. No extractable intent means no write; an interpretation outage quarantines the row and tells you, instead of masquerading as a verdict; bad input gets sanitized, not swallowed. Loud failure beats silent rot.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>memory</category><category>integrity</category><category>reliability</category><author>Curator</author></item><item><title>One GPU, every agent</title><link>https://blog.curatormcp.com/one-gpu-every-agent/</link><guid isPermaLink="true">https://blog.curatormcp.com/one-gpu-every-agent/</guid><description>Run several AI tools on one machine and they fight over a single graphics card. Curator can now ride a shared local inference backbone instead of loading its own model. It&apos;s opt-in, the default behavior is unchanged, and your memory layer and your orchestrator stop competing for the same hardware.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><category>local-llm</category><category>ecosystem</category><category>mcp</category><author>Curator</author></item><item><title>Curator ranks memory by truth, not by what&apos;s loudest</title><link>https://blog.curatormcp.com/ranked-by-truth-not-recency/</link><guid isPermaLink="true">https://blog.curatormcp.com/ranked-by-truth-not-recency/</guid><description>Most AI memory hands back whatever is newest or most similar, burying the standards you actually hold. Curator ranks recall by how well-established a memory is, so a durable decision beats this morning&apos;s status note.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate><category>memory</category><category>ranking</category><category>recall</category><author>Curator</author></item><item><title>Your agent forgets who you&apos;ve become. The stack fixes that.</title><link>https://blog.curatormcp.com/curator-in-the-agent-stack/</link><guid isPermaLink="true">https://blog.curatormcp.com/curator-in-the-agent-stack/</guid><description>Static memory hoards old facts; RAG retrieves frozen ones. Curator applies what&apos;s changed since, and paired with the rest of the stack, your agent finally knows both your code and you.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate><category>ecosystem</category><category>memory</category><author>Curator</author></item><item><title>Static, RAG, and the memory category nobody shipped</title><link>https://blog.curatormcp.com/the-memory-category-nobody-shipped/</link><guid isPermaLink="true">https://blog.curatormcp.com/the-memory-category-nobody-shipped/</guid><description>Everyone sells AI memory. Almost all of it remembers what you said and quietly forgets that you changed. Here is the category we are building instead.</description><pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate><category>memory</category><category>ai-agents</category><category>mcp</category><author>Curator</author></item><item><title>MCP is great alone. Paired with TheAuditor or Warden, it&apos;s hard to beat.</title><link>https://blog.curatormcp.com/mcp-better-with-warden-and-theauditor/</link><guid isPermaLink="true">https://blog.curatormcp.com/mcp-better-with-warden-and-theauditor/</guid><description>Curator gives your agent memory over the Model Context Protocol. Memory is one leg of a tripod. Here&apos;s what happens when you add the other two.</description><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate><category>mcp</category><category>ecosystem</category><category>ai-agents</category><author>Curator</author></item><item><title>Resume with what you know now</title><link>https://blog.curatormcp.com/resume-with-what-you-know-now/</link><guid isPermaLink="true">https://blog.curatormcp.com/resume-with-what-you-know-now/</guid><description>You&apos;re not the developer you were a year ago. Your old projects shouldn&apos;t pretend you are.</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>memory</category><category>resume-diff</category><category>workflow</category><author>Curator</author></item></channel></rss>