When Agent Context Goes Stale: Incoherence in Volatile Agent Context
Not on the map. Why?
Abstract (arXiv)
Modern agents increasingly ground their reasoning in observations returned by tools, such as file contents read from a workspace. However, the data sources underlying these observations may later be modified by users, other agents, or external tools, while the model retains only the stale content in its context window. Existing agent runtimes provide little support for notifying the model that a previously observed fact has become stale, causing agents to reuse outdated observations and make incorrect claims about the current workspace state. We propose Concord, a context coherence framework that maintains the consistency between tool observation in agent context and the mutable sources from which they were derived. Concord links each observation to its source, detects source changes, and uses configurable handling policies to update, annotate, or suppress stale context before reuse. Concord is applicable across different agent runtimes and external resources, and can be easily extended to new runtime-resource settings. We implement Concord as a general framework, and instantiate a concrete use case to assess its effectiveness. We construct ConcordBench, where previously observed file contents become stale after subsequent edits. Across three evaluated frontier models, Concord produces answers consistent with the restored workspace state in all evaluated cases under these constructed conditions, matching the oracle on recover count for this benchmark, while using 46.4% fewer tokens than the strongest non-oracle baseline.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 14 of its 21 references that are in the map. First posted on arXiv 4 Oct 2026.
Builds on
14 of 21 references.
References · 14
- 2018HotpotQA: A Dataset for Diverse, Explainable Multi-hop Question Answeringcited by 3,754
- 2023MetaGPT: Meta Programming for A Multi-Agent Collaborative Frameworkcited by 1,808
- 2024OpenHands: An Open Platform for AI Software Developers as Generalist Agentscited by 1,002
- 2026STALE: Can LLM Agents Know When Their Memories Are No Longer Valid?cited by 50
- 2026Supersede: Diagnosing and Training the Memory-Update Gap in LLM Agentscited by 20
- 2026Effective Strategies for Asynchronous Software Engineering Agentscited by 16
- 2025CodeCRDT: Observation-Driven Coordination for Multi-Agent LLM Code Generationcited by 11
- 2026Self-GC: Self-Governing Context for Long-Horizon LLM Agentscited by 11
- 2026InfiAgent: An Infinite-Horizon Framework for General-Purpose Autonomous Agentscited by 10
- 2026Verified Detection and Prevention of Concurrency Anomalies in Multi-Agent Large Language Model Systemscited by 8
- 2026Multi-agent Collaboration with State Managementcited by 6
- 2026ConflictRAG: Detecting and Resolving Knowledge Conflicts in Retrieval Augmented Generationcited by 4
Built on by
Not cited yet.