Agentic Context Management: Solving Agent Memory and Cost by Treating Them as Lifecycle and Architecture Problems
Agent memory should be a managed lifecycle, not just a database, to cut cost and forgetting.
92.0%
LongMemEval overall accuracy
Uses the smaller gpt-5-mini as both answer model and judge.
How it works
Agents drown in history
Re-sending the full chat every turn makes token cost grow quadratically. Crude summaries drop key facts and hurt accuracy.
Five-part context lifecycle
Design memory per agent, extract structure, scope retrieval by user and org, prefetch ahead, and compact with validation.
High memory benchmark scores
Synap scores 92.0% on LongMemEval and 93.2% on LoCoMo. Multi-session reasoning stays weakest at 75.2%.
What they found
Which comes out on top on LongMemEval category accuracy?
Bounded context savings over time
try itDrag conversation length up and watch token savings versus full-append grow.
- Token savings
- medium
- here
- Short chats: small savings
Terms
6 termsFull-append Re-sending the entire conversation history to the model on every turn.
Like a good executive assistant: files notes carefully, pulls the right folder before a meeting, and hands you a one-page brief checked against the originals.
Limits
- Core mechanisms are proprietary, so results cannot be independently reproduced in detail.
- No latency or token-cost measurements; savings figures are illustrative math.
- Competitor scores are self-reported with different setups, not a controlled comparison.