Topic

Memory

What agents remember, who may read it, and how it stays current.

All technical writing

2026

  1. Agent memory that remembers the current answer

    Building a multi-tenant memory service where identity bounds access, later facts supersede earlier ones, and tests grade the final answer rather than retrieval.

    SelectedMemoryEvaluationSecurity

  2. Making an agent’s memory useful without slowing its next reply

    Capture, evidence, retrieval, projection and delivery can each fail alone. A small replay found a fact lost before search could see it, and 92 live calls carried no receipt that any memory had arrived.

    SelectedAgent systemsMemoryRetrievalPerformance

  3. Compacting agent conversations without losing the source

    How a compaction ledger keeps instructions verbatim, ties each fact to the journal entries behind it, and recovers original evidence within a fixed scope.

    Agent systemsMemoryVerification

  4. Evidence should belong to the run that used it

    How per-run source rows, revision checks and publication-time binding keep a research report tied to the evidence it used, and what that doesn't prove.

    Agent systemsMemoryVerification

  5. Forgetting a memory must survive the retry that created it

    How a delayed create can bring a deleted memory back, and what stops it: durable operation receipts, a tombstone that keeps only the ID, supersession edges moved before a duplicate is forgotten, and recall whose staleness has a stated bound.

    SelectedMemoryStorageAgent systemsReliability

  6. Reducing allocation churn in an agent platform

    Why an agent gateway with broad retained state allocated gigabytes a minute, how repeated sizing and serialization drove it, and what bounded buffers and encode-once paths do and don't fix.

    PerformanceMemoryProfilingTypeScriptAgent systems