When Agent Context Goes Stale: Incoherence in Volatile Agent Context
cs.AI, cs.OS
Submitted: 2026-10-04
Updated: 2026-10-06
Comments: 8 pages, 3 figures, 1 table. Accepted to the AgenticOS Workshop at SOSP 2026
Code: https://github.com/crystaldba/postgres-mcp
License: http://creativecommons.org/licenses/by/4.0/
The gist: Modern agents increasingly ground their reasoning in observations returned by tools, such as file contents read from a workspace.
Abstract
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.
Sources
- STALE: Can LLM Agents Know When Their Memories Are No Longer Valid?
- Effective Strategies for Asynchronous Software Engineering Agents
- Self-GC: Self-Governing Context for Long-Horizon LLM Agents
- Verified Detection and Prevention of Concurrency Anomalies in Multi-Agent Large Language Model Systems
- Multi-agent Collaboration with State Management
- Governed Shared Memory for Multi-Agent LLM Systems
- Supersede: Diagnosing and Training the Memory-Update Gap in LLM Agents
- CodeCRDT: Observation-Driven Coordination for Multi-Agent LLM Code Generation
- LemonHarness Technical Report
- When Agents Overtrust Environmental Evidence: An Extensible Agentic Framework for Benchmarking Evidence-Grounding Defects in LLM Agents
- ConflictRAG: Detecting and Resolving Knowledge Conflicts in Retrieval Augmented Generation
- Less Context, More Accuracy: A Bi-Temporal Memory Engine for LLM Agents Where a Lean Retrieved Context Beats the Full History
- LLM Agents Are Latent Context Managers: Eliciting Self-Managed Context via State Proprioception
Related papers
- MAVEN-T: Reinforced Heterogeneous Distillation for Real-Time Multi-Agent Trajectory Prediction
- Model Discovery Agent: LLM-assisted Bayesian experiment design for data-efficient discovery of mechanistic world models
- Agents' Last Exam
- The Clinician's Veto: Navigating Trust, Liability, and Uncertainty in Autonomous AI Prescribing
- MindHelper: Closed-Loop Embodied Mental-State Reasoning for Precision Intervention
- Incumbent Advantage: Brand Bias and Cognitive Manipulation Dynamics in LLM Recommendation Systems