Curator blog
Product thinking, technical lessons, and release-preparation updates from Curator, evolutionary memory for AI agents. Part of the Code Reality Labs stack.
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.
Read post →
Most memory only remembers a decision and hopes the agent reads it. Curator now enforces at the moment of the edit, so a change that violates a recorded decision gets blocked before it lands.
Read post →
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.
Read post →
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.
Read post →
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.
Read post →
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.
Read post →
Most memory layers degrade quietly: they'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.
Read post →
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's opt-in, the default behavior is unchanged, and your memory layer and your orchestrator stop competing for the same hardware.
Read post →
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's status note.
Read post →
Static memory hoards old facts; RAG retrieves frozen ones. Curator applies what's changed since, and paired with the rest of the stack, your agent finally knows both your code and you.
Read post →
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.
Read post →
Curator gives your agent memory over the Model Context Protocol. Memory is one leg of a tripod. Here's what happens when you add the other two.
Read post →
You're not the developer you were a year ago. Your old projects shouldn't pretend you are.
Read post →