🤖 AI Summary
This work addresses the challenges of cross-session state persistence, user preference retention, and procedural knowledge accumulation in enterprise-grade, long-horizon AI agents by proposing a native memory architecture built upon Oracle Database. The architecture employs a hierarchical design that decouples active memory from passive storage, supports fine-grained scope control, and encompasses the full lifecycle of memory management. By integrating mechanisms for memory ingestion, retrieval, summarization, and revision, the system achieves 93.8% accuracy on the LongMemEval benchmark—significantly outperforming a flat-history baseline while reducing token consumption by approximately 10.7×. This approach substantially enhances memory efficiency and task performance without compromising low latency or high precision.
📝 Abstract
Agent memory is a systems problem for long-horizon agents. Practical deployments require retention of task state across extended conversations, recovery of user-specific facts and preferences across sessions, and accumulation of procedural knowledge from prior outcomes. These requirements extend beyond document retrieval: a memory layer must determine which interactions become durable state, how that state is scoped, how it is retrieved under latency constraints, and how it is revised or removed over time. This report studies Oracle Agent Memory as a database-native memory substrate built on Oracle Database. Three themes organize the discussion: memory as a lifecycle spanning ingestion, extraction, consolidation, retrieval, summarization, and revision or removal; a layered architecture that separates an active memory core from a passive memory-store interface with explicit scope control across users, agents, and threads; and evaluation methodology in which downstream task accuracy is complemented by memory-centric measures such as evidence retrieval, recall, latency, and estimated token use. The report summarizes LongMemEval results, reaching 93.8% accuracy, compares Oracle Agent Memory against flat-history baselines, using about 10.7x fewer tokens, and published or reported external baselines where available, and closes with implementation-oriented appendix material covering setup, thread lifecycle, and search semantics.