BudgetBench: Budget-Tiered Protocol for Evaluating Memory in Local LLM Agents

Researchers introduce BudgetBench, a protocol and pilot test harness for assessing memory strategies in locally run large language model agents. The work treats active context as a limited resource, accounting for memory capacity, prefill latency, cache growth, and service targets when deciding how many input tokens a call can afford. It aims to give a structured, budget-aware way to compare agent memory approaches under constrained hardware and latency conditions.

MemRiskBench Benchmark Targets Memory Risks in Long-Horizon LLM Agents

A new arXiv paper introduces MemRiskBench, an evaluation framework for long-horizon LLM agents that accumulate memory across sessions. It measures per-risk failure rates for issues such as stale facts, conflicting updates, cross-user data leakage, reuse of revoked memories, and decay of constraints, which aggregate scores tend to obscure. The work argues for trace-aware evaluation that preserves these distinct risk categories rather than collapsing them into a single number.

CoMem Paper Proposes Shared and Individual Memory Design for LLM Multi-Agent Systems

A new arXiv preprint introduces CoMem, a memory framework for LLM-driven multi-agent systems that combines collective knowledge with agent-specific memory. The authors argue that most existing approaches rely on flat, unstructured memory, which limits how agents learn and improve over time. The work targets better long-term cooperation and performance in evolutionary multi-agent setups.

Paper Proposes Environment-Probing Curation for Enterprise Agent Memory

A new arXiv paper addresses how persistent memory is being adopted in production agent platforms so long-horizon agents can retain experience across sessions. The authors argue that curator agents limited to completed task traces can lock in mistakes and draw overly broad conclusions from incomplete evidence, and propose probing the environment as an alternative approach to memory curation.

Hugging Face shows how to give coding agents persistent memory you control

A new Hugging Face blog post walks through building a memory layer for coding agents that remains under the developer's ownership instead of depending on external services. It explains how to store and reuse context such as past tasks, decisions, and code history so an agent can resume work across sessions. The guide favors open, self-hostable setups for keeping project knowledge local.

WHY IT MATTERS ↘Memory is emerging as a key differentiator for coding agents, but most commercial memory features are vendor-hosted, locking teams' accumulated project knowledge into external services. An open, self-hostable alternative addresses governance, data-residency, and lock-in concerns, making it more viable for enterprises to adopt agents while keeping proprietary context in-house.