🧠 AI Memory Monthly | November 2025

Context engineering and agent memory clicked into one discipline. Research recently formalized policies for what to keep, update, forget, and revisit; tooling shipped to make stateful agents durable; and the community sharpened the “RAG ≠ memory” distinction with real production notes. If you’re not designing how contexts evolve and how memories dynamically change, you’re leaving accuracy and cost on the table.

Treat them as one loop: each turn updates a policy-managed store (episodic notes, profiles, graphs) and curates what re-enters the next prompt. Recent work formalizes the loop and shows why forward-only “memorize while reading” loses critical evidence and collapses nuance over time.

Long documents or multi-step tasks spread key evidence across turns; single-pass write/overwrite drops it.

Add callback or revisitable memory so the agent can jump back to earlier evidence during planning or tool use. Reward not just final answers but use of memory (dense, step-level rewards).

ReMemR1 reports significant gains on long-doc QA when agents learn to revisit earlier evidence instead of overwriting it. Educator’s takeaway: design an explicit “revisit” action in the agent graph; don’t rely on the model to “remember” passively. arXiv

User preferences drift; naive updates either don’t adapt or overfit to one-off turns.

Use dual-horizon updates (e.g., Sliding Window + EMA) to fuse short-term fluctuations with long-term tendencies in a single vector/profile.

PAMU’s preference-aware update improves long-term dialog quality across LoCoMo scenarios by blending SW and EMA, a simple recipe you can implement in any store. arXiv

Memory bloat and contradictions degrade retrieval and raise cost.

• Entropy-minimizing decay: down-weight or delete items that do not reduce global predictive uncertainty (works well in affective/personalization settings).

• Multi-scale consolidation: coarse-grain episodic fragments into scenarios → traits, keeping stable signals while compressing detail.

New work proposes Bayesian/entropy-based updates to fight staleness and bloat, and RGMem shows multi-scale (“coarse-grain”) evolution yields more stable user profiles. arXiv-1,arXiv-2

• Agentic Context Engineering (ACE): Evolving Contexts for Self-Improving LMs (Oct 6): Structures how contexts (incl. agent memory) are generated → reflected on → curated; +10.6% on agent benchmarks in paper. arXiv

• Enabling Personalized Long-term Interactions via Persistent Memory & User Profiles (Oct 9) — Framework + small user study; stitches profiles + persistent memory. arXiv

• EcphoryRAG (Oct 10): KG-RAG inspired by human associative recall; entity-cue multi-hop retrieval; reports big EM lifts while cutting tokens. arXiv

• PISA: A Pragmatic Psych-Inspired Unified Memory System for Enhanced AI Agency (Oct 12): Practical framework combining persistent memory + evolving user profiles, evaluated on 3 datasets and a 5-day pilot study on perceived personalization. arXiv

• Context Engineering 2.0: The Context of Context Engineering (Oct 30): A clear, historically grounded definition of “context engineering” you can use to align prompt/policy work with memory design. arXiv

• Dynamic Affective Memory Management (DABench) (Oct 31): Proposes an entropy-minimizing memory update (treat each memory as a confidence distribution) and a benchmark focused on emotional coherence. arXiv

• “What memory system do you actually use?”

  A fresh poll-style thread favors Mem0 (OpenMemory via MCP) for quick wins, but folks still want graphs + vectors together for richer recall (game state, IDE copilots, etc.).
  If your domain has relations (entities, timelines), plan a graph store from day one - even if you start with vectors. Reddit

• “What tools peers are trying (smaller names you may have missed)”

  A roundup thread surfaces Memex (personal KGs), Recall.ai (session tracking), beads (issue-centric memory), context-pack (chat profile extraction) - useful for niche workflows. Reddit

• “Durable agents need a shared, persistent memory”

  A hands-on post shows LangGraph + cognee wired so multiple agents share a semantic memory over a knowledge graph (with code, sessionization, and visualizers). Reddit

• “Infinite memory” threads converge on tiered storage + lazy retrieval

  A month-old r/RAG build log collects pragmatic tips from the crowd: tiered memory (fast recent cache + archival DB), lazy loading, file-system “memory folders” for app-specific state, plus a roll-call of tools people are actually trying (Mem0, papr.ai, Zep/Graphiti, cognee). Reddit

• Cognee hosts office hours every Friday at 5 PM (CET) - join and ask your questions directly to the founder. You are invited.

• We have recently been to Weekly Community Tech Talk by Context Engineers community. Join the next one here.

• More to be announced.

What’s one policy (among what we discussed: keep/update/decay/revisit) that moved your agent’s real-world metrics the most?

Share it on r/AIMemory or drop your take in Discord; we will feature it next issue.

Send this to a friend who wants to build a durable agent that stay accurate and cheap.