earlyink
217 first flagged22 Oct 2026

Memory Bake-off: test Mem0, Zep and plain search on your own agent logs before you buy

Harness that replays your conversations through memory systems and raw-history search, scoring answers and cost. Agent builders pay.

Competitive · MemoryTax questions designed agent memory

Written for: Solo builder

Next step

This week, wrap LoCoMo plus a BM25 baseline and Mem0's open-source package in one CLI that runs against a JSONL log. Post the first comparison in the Latent Space Discord and r/LocalLLaMA.

Why now

Memory layers are a funded product category, and now there is a public method suggesting they may not beat a strong model with grep. Every team adding memory has to answer this for their own data, and the paper ran on only one conversation. An earlier card framed memory as an attack surface. This one is about whether memory pays for itself.

What became possible

The MemoryTax paper ran full context, BM25, Mem0 and Zep against three coding agents that search raw history with their own tools, across several models, on a 419-turn conversation with 152 questions. It asks whether designed memory still helps once the model can search for itself. Separately, Cache Engineering for Agents argues that editing history breaks KV caches and raises cost.

One way in

  1. memory-bakeoff

    Import chat or agent logs, auto-generate recall questions, then run each memory backend and an agent-search baseline. Report accuracy, tokens, latency and cache hit rate.

    Customer
    Startups building assistants and companion apps with long conversations
    Model
    Open-source runner, $199 hosted report on private logs

Competition

Competitive

Several open-source harnesses already compare memory backends side by side: Supermemory's MemoryBench, memeval, memtrust and EverMind's framework. Almost all of them are run by memory vendors, and they score public benchmarks like LoCoMo and LongMemEval rather than the customer's own conversations.

Full competition notes (7 competitors)

Several open-source harnesses already compare memory backends side by side: Supermemory's MemoryBench, memeval, memtrust and EverMind's framework. Almost all of them are run by memory vendors, and they score public benchmarks like LoCoMo and LongMemEval rather than the customer's own conversations. Those benchmarks have contested methodology, and the LoCoMo license restricts commercial use. None of the sources I found offered a neutral product that does the full workflow end to end: import production chat or agent logs, generate recall questions from them (including contradiction and time-changing facts), then report accuracy, tokens, latency and cost against a plain full-history or grep/agent-search baseline. Several sources explicitly say "run your own eval on your own data" and note that independent cross-vendor testing is thin, which is evidence of real demand. A new entrant could win on vendor neutrality, on generating questions from private logs with privacy safeguards, and on cost-per-correct-answer reporting that includes the plain-search baseline. The risks are that MemoryBench can add a bring-your-own-logs mode cheaply, that general LLM-eval platforms like Braintrust or Langfuse can approximate this with custom datasets, and that buyers may treat it as a one-time evaluation rather than a recurring subscription. Continuous regression testing after a memory system is adopted may be the more durable thing to sell.

  • Supermemory MemoryBench

    Open-source harness from the memory vendor Supermemory. It has provider adapters for Supermemory, Mem0 and Zep, runs LoCoMo, LongMemEval and ConvoMem, and accepts contributed providers and benchmarks. It is the closest existing match, but a competing vendor runs it and it centers on public benchmarks rather than your own logs.

  • memeval (PyPI memoryeval)

    Open-source pytest-style evaluation framework with adapters for Mem0, Zep, Letta and an in-memory store. It supports custom YAML scenarios, such as checking whether corrections propagate. Scenarios are hand-written; it does not generate questions automatically from imported logs.

  • memtrust

    Open-source benchmark harness that runs the same LongMemEval, LoCoMo and contradiction evals against mempalace, mem0, zep and openviking, and publishes the raw logs. Aimed at public benchmarks.

  • EverMind unified evaluation framework

    Another memory vendor's framework that compares EverOS, Mem0, MemOS, Zep and MemU through their online APIs, using the same datasets, metrics and answer model. Vendor-run and based on benchmarks.

  • Mem0 memory evaluation docs

    Mem0 publishes evaluation guidance and tooling that track accuracy, token cost and latency, but this mostly serves its own benchmark claims.

  • Zep evaluation guidance and benchmark critique

    Zep disputes Mem0's LoCoMo methodology and notes that a full-context baseline beat Mem0. This shows that vendor benchmark numbers are contested, which is the core pain point.

  • Cognee guide to evaluating AI memory tools

    Compares what each memory tool exposes for evaluation. Cognee is also a memory vendor with its own eval tooling.

Checked 2026-10-22

Risks

  • Auto-generated questions may not match how real users ask
  • Memory vendors may dispute results, and benchmark fights eat time
  • The market is small: only teams with long-lived conversations care

Strong tech readiness and team fit; market pull is the weak point (5).

tech 8 · pull 5 · space 7 · fit 8 · build 8

Momentum of its main topic

175 developments this week +33 vs last week
23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 32 developments9 Oct: 26 developments10 Oct: 13 developments11 Oct: 11 developments12 Oct: 14 developments13 Oct: 19 developments14 Oct: 24 developments15 Oct: 35 developments16 Oct: 31 developments17 Oct: 15 developments18 Oct: 14 developments19 Oct: 23 developments20 Oct: 26 developments21 Oct: 36 developments22 Oct: 30 developments
Stage: Coverage

Sources

  1. MemoryTax: The Bitter Lesson of Agent MemoryarXiv
  2. Cache Engineering for AgentsHF Daily Papers

Status history

  • 2026-10-22 Flagged as buildable