Memori: A Persistent Memory Layer for Efficient, Context-Aware LLM Agents 

Report GitHub Issue

 × 

 Title: 

Content selection saved. Describe the issue below:

 Description: 

 Submit without GitHub 
 Submit in GitHub 

 Back to arXiv 

 Why HTML? 

 Report Issue 

 Back to Abstract 

 Download PDF 

 Abstract 

 1 Introduction 

 2 System Architecture 

 2.1 Advanced Augmentation: Structuring the Unstructured 

 3 Experiments 

 3.1 Dataset: The LoCoMo Benchmark 

 3.2 Evaluating Memory Extraction via Advanced Augmentation 

 3.3 Answer Generation 

 3.4 Performance Metrics: LLM-as-a-Judge 

 3.5 Token-Driven Cost Analysis 

 3.6 Results and Analysis 

 3.7 Overall Performance 

 3.8 Performance by Category 

 3.9 Token Usage and Cost Efficiency 

 4 Conclusion 

 A Appendix A 

 B Appendix B 

 C Appendix C 

 References 

 License: CC BY 4.0

arXiv:2603.19935v1 [cs.LG] 20 Mar 2026

Memori: A Persistent Memory Layer for Efficient, Context-Aware LLM Agents

Luiz C. Borro 

Memori Labs Inc. 

 luiz@memorilabs.ai 

 Luiz A. B. Macarini 

Memori Labs Inc. 

 lmacarini@memorilabs.ai 

 Gordon Tindall 

Memori Labs Inc. 

 gordon@memorilabs.ai 

 Michael Montero 

Memori Labs Inc. 

 mike@memorilabs.ai 

 Adam B. Struck 

Memori Labs Inc. 

 adam@memorilabs.ai 

Abstract

As large language models (LLMs) evolve into autonomous agents, persistent memory at the API layer is essential for enabling context-aware behavior across LLMs and multi-session interactions. Existing approaches force vendor lock-in and rely on injecting large volumes of raw conversation into prompts, leading to high token costs and degraded performance.
We introduce Memori, a LLM-agnostic persistent memory layer that treats memory as a data structuring problem. Its Advanced Augmentation pipeline converts unstructured dialogue into compact semantic triples and conversation summaries, enabling precise retrieval and coherent reasoning.
Evaluated on the LoCoMo benchmark, Memori achieves 81.95% accuracy, outperforming existing memory systems while using only 1,294 tokens per query ( ∼ \sim 5% of full context). This results in substantial cost reductions, including 67% fewer tokens than competing approaches and over 20 × \times savings compared to full-context methods.
These results show that effective memory in LLM agents depends on structured representations instead of larger context windows, enabling scalable and cost-efficient deployment.

Code: https://github.com/MemoriLabs/Memori 

 Keywords  LLM Memory Systems ⋅ \cdot 
Context-Efficient Retrieval ⋅ \cdot 
Semantic Triples Representation

 1 Introduction

Large language models (LLMs) have quickly become sophisticated AI agents. These foundation-model-powered systems perform well in research, software engineering, and scientific discovery, driving the move toward general intelligence (Hu et al. , 2025 ) . Modern agents now go beyond using only LLMs by adding reasoning, planning, perception, memory, and tool use (Xi et al. , 2025 ) . These components let LLMs act as adaptive systems that interact with their environments and improve over time.

Among these capabilities, memory stands out as a foundational pillar. Unlike reasoning or tool use, which are increasingly internalized within model parameters, memory remains largely dependent on external system design. This dependency arises because LLM parameters cannot be updated in real time during deployment (Shinn et al. , 2023 ) . Memory mechanisms, therefore, play a key role in enabling agents to persist information across interactions, adapt to user context, and evolve based on experience (Packer et al. , 2023 ) .

This reliance on external memory is especially apparent from an application perspective: persistent memory is essential (Hu et al. , 2025 ) . Domains such as personalized assistants, recommendation systems, social simulations, and complex investigative workflows all require agents to retain and reason over historical information (Zhong et al. , 2024 ; Hu et al. , 2025 ) . Without memory, these systems behave as stateless responders, repeatedly reprocessing context and failing to build continuity over time (Packer et al. , 2023 ; Wang et al. , 2024 ) . From a broader research perspective, agents’ ability to continually evolve through interaction is central to the pursuit of general intelligence. This capacity is fundamentally grounded in memory.

Enabling long-term, cross-session, cross-model memory introduces significant challenges. Naively storing and injecting past interactions into the prompt leads to rapidly growing context windows. This increases both cost and instability. As context size grows, models become more prone to overlooking critical information. They may produce inconsistent outputs and suffer from what is commonly referred to as context rot , in which relevant information is present but not effectively used (Hong et al. , 2025 ) .

These limitations highlight a key insight: memory in LLM systems is not simply a storage problem, but a structuring problem. The challenge is to transform noisy, unstructured conversational data into representations that are efficient to retrieve. These representations must also be effective for downstream reasoning.

Memori implements this as a persistent memory layer that incrementally distills conversational data into structured representations. This process is handled by Advanced Augmentation, a memory creation pipeline that extracts, compresses, and organizes high-signal information from raw interactions for efficient retrieval and downstream use. Through empirical evaluation on the LoCoMo benchmark, we demonstrate that high-quality memory structuring enables strong reasoning performance while reducing the number of tokens required in the prompt, thereby improving the cost-efficiency and scalability of LLM agents.

 2 System Architecture

As depicted in Figure 1 , Memori operates as a decoupled memory layer positioned between the application logic and the underlying LLM. The system integrates via a lightweight Memori SDK, seamlessly wrapping existing LLM clients to intercept requests and manage memory natively.

 Figure 1: High-level architecture illustrating the system’s structure, data flow, and the interaction between its core components. 

The core differentiators of the Memori architecture lie in how it structures unstructured data and how it intelligently retrieves that data for reasoning.

 2.1 Advanced Augmentation: Structuring the Unstructured

Raw conversation logs are noisy, filled with colloquialisms, pleasantries, self-corrections, and tangential discussions. When these raw, unstructured transcripts are directly chunked and embedded, as is standard in traditional RAG architectures, the resulting vector space becomes heavily cluttered. Direct retrieval from this noisy data is highly inefficient, leading to false positives, contradictory context, and massively inflated token consumption during the generation phase.

To solve this, Advanced Augmentation functions as an automated cognitive filter. It is a background memory creation pipeline designed to distill raw dialogue into searchable memory assets, shifting the system’s memory from mere text storage to an organized knowledge base.

 • 

 Semantic Extraction & Triple Generation: Rather than saving sentences, the pipeline deconstructs dialogue messages into atomic units of knowledge. It actively scans conversations for concrete facts, user preferences, constraints, and evolving attributes, structuring them into semantic triples (subject–predicate–object). Each triple is then linked to the exact conversation in which it was mentioned. This design delivers two key advantages. First, it produces a low-noise, high-signal index that improves vector search retrieval accuracy. Second, it functions as a compression layer.

 • 

 Conversation Summarization: While semantic triples excel at capturing granular, static facts, they inherently strip away the surrounding context. An isolated triple might state what a user prefers, but it lacks the narrative of why a decision was made or how a user’s goal evolved throughout a specific interaction. To bridge this gap, the pipeline simultaneously generates Conversation Summaries. These are concise, high-level overviews of specific conversational threads that capture the user’s overarching intent, the dialogue’s chronological progression, and the task’s implicit context. Because triples are tied to their source, each individual triple can be directly linked to the proper summary of the conversation in which it appears, allowing the system to easily retrieve the background story behind any isolated fact.

Advanced Augmentation creates an interconnected, dual-layered memory asset: Triples provide the precise, token-efficient facts needed for exact recall, while Conversation Summaries provide the cohesive narrative flow required for the LLM to understand temporal changes and execute complex reasoning. By linking atomic triples directly to the summaries of the conversations they originated from, the system ensures that granular facts are never divorced from their broader context.

 3 Experiments

The primary objective of these experiments is to evaluate the quality and accuracy of the memory assets produced by Memori’s Advanced Augmentation pipeline.

 3.1 Dataset: The LoCoMo Benchmark

The primary dataset utilized for benchmarking is the Long Conversation Memory (LoCoMo) dataset (Maharana et al. , 2024 ) . LoCoMo is a rigorous framework engineered to evaluate an AI agent’s ability to track, retain, and synthesize information across extensive, multi-session chat histories. Unlike standard QA datasets, LoCoMo challenges models with complex state tracking, temporal reasoning, and the retrieval of subtle user preferences buried deep within noisy, unstructured conversational logs.

The category alignment and question distribution are detailed in Table 3 , presented in Appendix   C .

To ensure a fair comparison with other published results on this benchmark, we excluded the adversarial category from the evaluation (Chhikara et al. , 2025 ; Du et al. , 2025 ) .

 3.2 Evaluating Memory Extraction via Advanced Augmentation

To measure the quality of Memori’s Advanced Augmentation, all sections of each LoCoMo conversation were processed through the pipeline. Each session produced a set of semantic triples along with conversation-level summaries. The extracted triples were embedded using the Gemma-300 embedding model, enabling efficient semantic retrieval for the benchmark’s question-answering tasks. All generated memories were indexed and stored locally using FAISS to support fast similarity search. The ultimate accuracy of the LLM’s answers serves as a direct reflection of how well the Advanced Augmentation pipeline structured, preserved, and surfaced the relevant facts.

 3.3 Answer Generation

Each question in the LoCoMo benchmark was answered using GPT-4.1-mini, conditioned on the retrieved triples and their corresponding summaries (the utilized prompt is presented in the Appendix A ). Triples were retrieved using a hybrid search approach that combines cosine similarity over embeddings with BM25 keyword matching.

 3.4 Performance Metrics: LLM-as-a-Judge

We employ an LLM-as-a-Judge methodology (the utilized prompt is presented in the Appendix B ), using GPT-4.1-mini as the evaluator. The judge model analyzes the user query, the ground-truth answer, and the generated response to provide a nuanced assessment.

 3.5 Token-Driven Cost Analysis

Beyond response quality, practical deployment considerations are paramount for enterprise AI applications. We evaluate Memori against traditional architectures (e.g., standard RAG) by systematically measuring system efficiency as a function of context consumption.

The absolute number of tokens added to the LLM prompt is the primary driver of operational costs in conversational AI. We measure the exact number of tokens extracted during retrieval and injected into the prompt context. This metric highlights a critical architectural distinction: while traditional architectures consume massive token budgets by indiscriminately injecting large, raw text chunks or full histories into the prompt, Memori retrieves highly concise, structured memory facts. By minimizing the context footprint, Memori directly curtails API expenditure and optimizes operational economics.

 3.6 Results and Analysis

This section summarizes how Memori’s Advanced Augmentation performed on the LoCoMo benchmark. We compare Memori against established memory systems, including Zep 1 1 1 https://github.com/getzep/zep , LangMem 2 2 2 https://github.com/langchain-ai/langmem , and Mem0 3 3 3 https://github.com/mem0ai/mem0 , using their official open-source implementations. Using our LLM-as-a-Judge framework, we evaluated four reasoning categories (Multi-Hop, Temporal, Open-Domain, and Single-Hop) and compared Memori against several memory baselines and a Full-Context ceiling. We also examined the vital tradeoff between output accuracy and token cost efficiency. The results are presented in Table 1 .

 Table 1: LLM-as-a-Judge Evaluation Results on the LoCoMo Benchmark.
This table compares the factual accuracy and reasoning capabilities of Memori’s Advanced Augmentation assets against state-of-the-art baselines and a full-context ceiling. Memori performance values were computed using the average of three rounds. Results for Mem0, Zep, LangMem and Full-context were retrieved from Du et al. ( 2025 ) . 

 Method 
 Single-hop (%) 
 Multi-hop (%) 
 Open-domain (%) 
 Temporal (%) 
 Overall (%) 

 Memori 
 87.87 
 72.70 
 63.54 
 80.37 
 81.95 

 Zep 
 79.43 
 69.16 
 73.96 
 83.33 
 79.09 

 LangMem 
 74.47 
 61.06 
 67.71 
 86.92 
 78.05 

 Mem0 
 62.41 
 57.32 
 44.79 
 66.47 
 62.47 

 Full-Context (Ceiling) 
 88.53 
 77.70 
 71.88 
 92.70 
 87.52 

Graphical representation of the Memori’s average accuracy along with the standard deviation is presented in Figure 2 .

 Figure 2: Accuracy of Memori across different reasoning categories. Bar heights represent the mean accuracy (%), while error bars indicate the standard deviation for n = 3 n=3 runs. 

 3.7 Overall Performance

As expected, the Full-Context setup achieved the highest score (87.52%). However, passing the entire conversation history into the prompt is fundamentally impractical in production due to prohibitive token costs, uncontrolled context expansion, and context degradation over time.

Among retrieval-based systems, Memori achieved a leading overall score of 81.95%, successfully outperforming Zep (79.09%), LangMem (78.05%), and Mem0 (62.47%). This validates the assumption that by structuring unstructured chat logs into semantic triples and their summaries, Memori effectively isolates high-signal knowledge. This structured memory design significantly narrows the gap to the Full-Context ceiling while keeping context windows highly manageable and operational token costs low.

The reported overall scores for all methods were computed as a weighted average based on the number of questions in each LoCoMo category, as detailed in Table 3 , at Appendix C .

 3.8 Performance by Category

Analyzing the results across reasoning categories highlights the specific strengths of Memori’s extracted memory assets:

 • 

 Single-Hop Reasoning (87.87%): Memori excels in direct fact retrieval, outperforming both LangMem (74.47%) and Zep (79.43%). By minimizing conversational noise and structuring data cleanly, the LLM is fed exact, undeniable facts, minimizing token consumption while maximizing direct recall.

 • 

 Temporal Reasoning (80.37%): Memori outperforms Mem0 (66.47%) but trails LangMem (86.92%) and Zep (83.33%) in temporal tracking. Isolated semantic triples capture static facts but often miss the temporal context needed to identify changes in user states or preferences across sessions. Memori’s summaries help rebuild this timeline, but the results show it needs better temporal reasoning.

 • 

 Multi-Hop Reasoning (72.70%): Memori performs strongly when asked to connect disparate pieces of information, outperforming Zep (69.16%) and trailing LangMem (61.06%) by a narrow margin. The combination of precise triples and cohesive summaries provides the necessary backdrop that helps the LLM connect isolated facts without needing the entire conversational transcript injected into the prompt.

 • 

 Open-Domain Reasoning (63.54%): This category remains challenging across all retrieval-based systems. Open-ended questions often lack clear retrieval anchors, making them difficult to match with granular triples. Furthermore, these queries require broad synthesis across massive contexts rather than simple fact extraction. While Memori lags slightly behind LangMem (67.71%) here, it is important to note that improving open-domain scores typically requires retrieving significantly larger chunks of text, which actively works against the system’s core operational goal: strictly minimizing the number of tokens added to the context to control API costs.

 3.9 Token Usage and Cost Efficiency

Traditional memory architectures and standard RAG setups often rely on retrieving raw, uncompressed text chunks. This indiscriminately injects conversational noise and redundant dialogue into the prompt, consuming context limits and inflating API bills.

Memori’s Advanced Augmentation pipeline completely bypasses this inefficiency by acting as an intelligent cognitive filter. Rather than retrieving raw text, it compresses chat logs into structured representations, including dense semantic triples and concise conversation-level summaries. As a result, only high-signal, structured information is passed to the LLM, minimizing context overhead while preserving relevant context.

 Table 2: Token Usage and Cost Efficiency.
This table analyzes the operational efficiency of each method by measuring the absolute number of tokens added to the context and the resulting cost per query. Costs are computed based on current gpt-4.1-mini pricing: $0.8 per 1M tokens. Mem0, Zep and Full-Context values were retrieved from Chhikara et al. ( 2025 ) . 

 Method 
 Added Tokens to Context (mean) 
 Context Cost ($) 
 Context Footprint (%) 

 Memori 
 1,294 
 0.001035 
 4.97 

 Full-Context 
 26,031 
 0.020825 
 100.00 

 Mem0 
 1,764 
 0.001411 
 6.78 

 Zep 
 3,911 
 0.003129 
 15.02 

Memori requires an average of only 1,294 tokens to ground each LLM response. This token footprint represents just 4.97% of the full conversational context, while achieving the 81.95% overall accuracy detailed in the previous section.
When compared to competing memory frameworks, the operational advantages become even more pronounced:

 • 

C ompared to Zep (3,911 tokens): Memori reduces the prompt size by roughly 67% per query, directly cutting API inference costs by the same margin, while simultaneously delivering a higher accuracy score (81.95% vs. 79.09%).

 • 

 Compared to the Full-Context approach (26,031 tokens): Passing the entire history is financially unsustainable for persistent agents, costing over 20 times more per turn than Memori. Furthermore, repeatedly injecting 26K+ tokens drastically increases the risk of "lost in the middle" hallucinations.

 4 Conclusion

For LLM agents to scale in production, persistent memory must address two fundamental challenges: context degradation and rapidly increasing token costs. Memori approaches this not as a storage issue, but as a data structuring problem.

Through its Advanced Augmentation memory creation pipeline, Memori transforms noisy conversational logs into compact, high-signal representations, combining precise semantic triples with coherent conversation-level summaries. This dual representation enables accurate fact retrieval alongside strong temporal and contextual reasoning, without inflating the prompt with unnecessary tokens.

Our evaluation on the LoCoMo benchmark demonstrates the effectiveness of this approach:

 • 

 High-Quality Reasoning: Memori achieves state-of-the-art performance among retrieval-based systems, with particularly strong gains in temporal and single-hop reasoning - highlighting the impact of structured memory on reasoning fidelity.

 • 

 Minimal Context Footprint: Responses are grounded using a small fraction of the original conversation, showing that well-structured memory can replace large, unfiltered context without sacrificing accuracy.

 • 

 Cost-Efficient Scaling: By significantly reducing the number of tokens injected into the prompt, Memori directly lowers inference costs and enables sustainable deployment of long-running agents.

These results highlight a fundamental shift in memory design for LLM systems: performance is determined not by how much context is used, but by the quality of its structure.

Memori eliminates the traditional tradeoff between reasoning quality and operational cost. By delivering accurate, cross-session recall with a compact context footprint, it provides a practical and scalable foundation for deploying persistent AI agents in real-world environments.

 Appendix A Appendix A

Prompt Template for Results Generation (Chhikara et al. , 2025 ) .

 ⬇ 

 ANSWER_PROMPT = """ 

 You are an intelligent memory assistant tasked with retrieving accurate information from conversation memories . 

 # CONTEXT : 

 You have access to two types of information from a conversation : 

 - Memories : timestamped factual triples extracted from conversations . 

 - Summaries : high - level conversation summaries ( also timestamped ) that 

 provide broader context around the memories . 

 # INSTRUCTIONS : 

 1. Carefully analyze all provided memories and summaries 

 2. Pay special attention to the timestamps to determine the answer 

 3. If the question asks about a specific event or fact , look for direct evidence in the memories 

 4. If the memories contain contradictory information , prioritize the most recent memory 

 5. If there is a question about time references ( like " last year ", " two months ago ", etc .), 

 calculate the actual date based on the memory timestamp . For example , if a memory from 

 4 May 2022 mentions " went to India last year ," then the trip occurred in 2021. 

 6. Always convert relative time references to specific dates , months , or years . For example , 

 convert " last year " to "2022" or " two months ago " to " March 2023" based on the memory 

 timestamp . Ignore the reference while answering the question . 

 7. Focus only on the content of the memories . Do not confuse character 

 names mentioned in memories with the actual users who created those memories . 

 8. The answer should be less than 5-6 words . 

 # APPROACH ( Think step by step ): 

 1. First , examine all memories that contain information related to the question 

 2. Use summaries for broader context when memories alone are insufficient 

 3. Examine the timestamps and content carefully 

 4. Look for explicit mentions of dates , times , locations , or events that answer the question 

 5. If the answer requires calculation ( e . g ., converting relative time references ), show your work 

 6. Formulate a precise , concise answer based solely on the evidence in the memories 

 7. Double - check that your answer directly addresses the question asked 

 8. Ensure your final answer is specific and avoids vague time references 

 {{ memories }} 

 Question : {{ question }} 

 Answer : 

 """ 

 Appendix B Appendix B

Prompt Template for LLM-as-a-Judge (Chhikara et al. , 2025 ) .

 ⬇ 

 ACCURACY_PROMPT = """ 

 Your task is to label an answer to a question as ’ CORRECT ’ or ’ WRONG ’. You will be given the following data : 

 (1) a question ( posed by one user to another user ), 

 (2) a ’ gold ’ ( ground truth ) answer , 

 (3) a generated answer 

 which you will score as CORRECT / WRONG . 

 The point of the question is to ask about something one user should know about the other user based on their prior conversations . 

 The gold answer will usually be a concise and short answer that includes the referenced topic , for example : 

 Question : Do you remember what I got the last time I went to Hawaii ? 

 Gold answer : A shell necklace 

 The generated answer might be much longer , but you should be generous with your grading - as long as it touches on the same topic as the gold answer , it should be counted as CORRECT . 

 For time related questions , the gold answer will be a specific date , month , year , etc . The generated answer might be much longer or use relative time references ( like " last Tuesday " or " next month "), but you should be generous with your grading - as long as it refers to the same date or time period as the gold answer , it should be counted as CORRECT . Even if the format differs ( e . g ., " May 7 th " vs "7 May "), consider it CORRECT if it ’ s the same date . 

 Now it ’ s time for the real question : 

 Question : { question } 

 Gold answer : { gold_answer } 

 Generated answer : { generated_answer } 

 First , provide a short ( one sentence ) explanation of your reasoning , then finish with CORRECT or WRONG . 

 Do NOT include both CORRECT and WRONG in your response , or it will break the evaluation script . 

 Just return the label CORRECT or WRONG in a json format with the key as " label ". 

 """ 

 Appendix C Appendix C

This table presents the mapping between question categories in the LoCoMo dataset and their corresponding evaluation order, along with the number of questions in each category.

 Table 3: The alignment of the orders and categories in the LoCoMo dataset. 

 Multi-Hop 
 Temporal 
 Open-Domain 
 Single-Hop 
 Adversarial 

 Order 
 Category 1 
 Category 2 
 Category 3 
 Category 4 
 Category 5 

 # Questions 
 282 
 321 
 96 
 830 
 445 

References

 P. Chhikara, D. Khant, S. Aryan, T. Singh, and D. Yadav (2025) 
 Mem0: building production-ready ai agents with scalable long-term memory .

 External Links: 2504.19413 ,
 Link 

 Cited by: Appendix A ,
 Appendix B ,
 §3.1 ,
 Table 2 .

 X. Du, L. Li, D. Zhang, and L. Song (2025) 
 MemR 3 : memory retrieval via reflective reasoning for llm agents .

 arXiv preprint arXiv:2512.20237 .

 Cited by: §3.1 ,
 Table 1 .

 K. Hong, A. Troynikov, and J. Huber (2025) 
 Context rot: how increasing input tokens impacts llm performance .

 URL https://research.trychroma.com/context-rot, retrieved October 20 , pp. 2025 .

 Cited by: §1 .

 Y. Hu, S. Liu, Y. Yue, G. Zhang, B. Liu, F. Zhu, J. Lin, H. Guo, S. Dou, Z. Xi, et al. (2025) 
 Memory in the age of ai agents .

 arXiv preprint arXiv:2512.13564 .

 Cited by: §1 ,
 §1 .

 A. Maharana, D. Lee, S. Tulyakov, M. Bansal, F. Barbieri, and Y. Fang (2024) 
 Evaluating very long-term conversational memory of llm agents .

 External Links: 2402.17753 ,
 Link 

 Cited by: §3.1 .

 C. Packer, V. Fang, S. Patil, K. Lin, S. Wooders, and J. Gonzalez (2023) 
 MemGPT: towards llms as operating systems. .

 Cited by: §1 ,
 §1 .

 N. Shinn, F. Cassano, A. Gopinath, K. Narasimhan, and S. Yao (2023) 
 Reflexion: language agents with verbal reinforcement learning .

 Advances in neural information processing systems 36 , pp. 8634–8652 .

 Cited by: §1 .

 L. Wang, C. Ma, X. Feng, Z. Zhang, H. Yang, J. Zhang, Z. Chen, J. Tang, X. Chen, Y. Lin, et al. (2024) 
 A survey on large language model based autonomous agents .

 Frontiers of Computer Science 18 ( 6 ), pp. 186345 .

 Cited by: §1 .

 Z. Xi, W. Chen, X. Guo, W. He, Y. Ding, B. Hong, M. Zhang, J. Wang, S. Jin, E. Zhou, et al. (2025) 
 The rise and potential of large language model based agents: a survey .

 Science China Information Sciences 68 ( 2 ), pp. 121101 .

 Cited by: §1 .

 W. Zhong, L. Guo, Q. Gao, H. Ye, and Y. Wang (2024) 
 Memorybank: enhancing large language models with long-term memory .

 In Proceedings of the AAAI conference on artificial intelligence ,

 Vol. 38 , pp. 19724–19731 .

 Cited by: §1 .

 Experimental support, please
 view the build logs 
 for errors. Generated by

 L
 A 
 T
 E 

 xml 

 .

Instructions for reporting errors

We are continuing to improve HTML versions of papers, and your feedback helps enhance accessibility and mobile
 support. To report errors in the HTML that will help us improve conversion and rendering, choose any of the
 methods listed below:

Click the "Report Issue" ( 

 ) button, located in the page header.

 Tip: You can select the relevant text first, to include it in your report.

Our team has already identified the following issues . We appreciate your time reviewing and reporting rendering errors we
 may not have found yet. Your efforts will help us improve the HTML versions for all readers, because disability
 should not be a barrier to accessing research. Thank you for your continued support in championing open access for
 all.

Have a free development cycle? Help support accessibility at arXiv! Our collaborators at LaTeXML maintain a list of packages that need conversion , and welcome developer contributions .

BETA