Knowing what changed is not the same as learning what worked.
Zep builds temporal Context Graphs from conversations, business data and agent activity. Memco turns corrections, failed approaches and outcomes into scoped lessons, so a later engineer or agent inherits the useful shortcut, not only the history.
Different person · Different session · Different tool · Reused lesson
What is at stake
Your team already paid to learn the lesson. The next agent should not pay again.
Coding agents discover repository quirks, rejected approaches and working fixes every day. The useful part is rarely the whole transcript. It is the lesson that should change a later run, attached to the source, scoped to the right team and kept current when the code changes.
Fewer repeated mistakes
Later agents receive the known constraint before they repeat a failed approach.
Less senior re-explanation
Corrections stop dying in review comments, chat threads and one engineer’s memory.
Cross-tool continuity
The lesson survives when the team moves between Claude Code, Cursor, Codex, Copilot or internal agents, subject to actual integration support.
Customer-owned learning
The organization keeps the lesson, source and scope rather than renting the same rediscovery from each model or tool.
01Honest overlap
Where the products genuinely overlap.
Zep’s center of gravity is temporal context and contradiction-aware history. The overlap below is genuine — which is why the proof object on this page has to be different: a prior lesson improving later work across people and tools.
- 01Both products persist structured memory across sessions.
- 02Both preserve provenance for what they store.
- 03Both support scoped access to memory.
- 04Both connect memory to agent surfaces, including MCP paths for coding-agent clients.
02Where each product starts
Different centers of gravity.
Zep models changing context. Memco productizes how real work becomes reusable team learning.
Zep · temporal context graphs
Serve current and historical context about users, businesses, entities and events.
- Primary inputs: chat, text, JSON, business events and agent activity represented as Episodes.
- Outcome: the agent receives a governed account of what is true now and what was true before.
Memco · engineering learning
Convert real agent work into reviewed, scoped and reusable team lessons.
- Primary inputs: agent attempts, human corrections, failed paths, tests, review decisions, accepted fixes and downstream outcomes, according to released integration behavior.
- Outcome: the later engineering run receives an evidence-backed action that avoids a previously failed path.
03The visual argument
What changed, or what should the next run do differently?
Zep answers with a temporal context graph. Memco answers with an evidence-backed engineering lesson that carries its source, scope, review state and later outcome — and closes the loop when the next run reports back.
Zep moves episodes toward prompt-ready context. Memco moves real work through review and scope into later reuse and outcome feedback.
04The same week, replayed
One payment-retry bug. Two product jobs.
Illustrative engineering workflow — not customer evidence. The same scenario runs on every comparison page, so what differs is the product job, not the anecdote.
- 01Agent A · Cursorpayment-retry taskcalls a helper that was retired last quarter
- 02Failed testci · redthe dead end costs the run its first hour
- 03Senior correctionreview + passing PRthe durable fact: which path works now, and why
- 04Scoped reviewed lessonteam scope · provenance keptsource, reviewer, scope and outcome attached
- 05Agent B · Claude Codenext week · different personstarts ahead of the dead end
Zep can represent the helper, the source events, the change in validity and when the old pattern stopped being current.
Memco focuses the reusable object on the action, source, scope, review and later engineering outcome, then tests whether another agent avoided the old helper.LESSON MEM-4821 ACTION use retry_payment_v2 AVOID legacy_retry SCOPE payments-service / Payments team SOURCE corrected PR + passing integration test STATE reviewed PROOF later task avoided the retired helperIllustrative payload — not a live customer record or current UI
05Practical comparison
Dimension by dimension, in words.
Rows, not scoreboards: each dimension states what each product actually does, so the difference survives scrutiny.
06Choose honestly
Two good answers to two different questions.
Choose Zep if
- ‘What was true at that time?’ is a first-class product requirement.
- Production agents need temporal user, account or business context.
- Episodes, validity windows, Context Graphs and Observations are the desired substrate.
- Broad governed context infrastructure is the primary buying job.
Choose Memco if
- A lesson from one person’s agent should improve a later task for another person or tool.
- Corrections, failed paths and accepted outcomes keep getting rediscovered.
- Shared learning needs source, scope, review and a path to correction or retirement.
- The organization wants its learning to survive model, IDE and agent-platform changes.
07Proof, not vibes
The reuse test.
Do not stop at “the agent remembered.” If the main job is serving current and historical context about users, businesses, entities and events, evaluate Zep. If the job is to make real engineering learning travel safely across people and tools, run the Memco reuse test.
A signup is not activation. Activation is a lesson contributed from one task and correctly reused on a later task.
08Enterprise confidence
Governed by construction.
Shared memory becomes infrastructure. Treat it like infrastructure. Private company memory stays inside your organisation — there is no public pool for it to reach.
09Questions
What evaluating teams ask.
Source ledger
Statements about Zep are drawn from its official documentation and site, reviewed on 2026-07-30. Products change — if anything here is out of date, tell us and we will correct it.
- 01Zep — Temporal Context Graph positioning
- 02Zep — core concepts and Episodes
- 03Zep — graph-derived Observations
- 04Zep — enterprise deployment and controls
- 05Zep — security and compliance documentation
- 06Zep — Memory MCP
- 07Zep — Graphiti MCP
- 08Zep — current pricing
- 09Memco — product positioning and shared-memory focus
- 10Memco — team pricing and memory controls
- 11Memco — product and integration documentation
- 12Memco — making sense of agentic memory
- 13Memco — active memory: reinforcement learning for agents
- 14Memco — the art of forgetting
Test whether one lesson can improve the next run.
the loop
benchmarks · product · research
A short dispatch on shared memory for AI agents — the numbers behind the product, what we're shipping, and the research we're reading. No filler.