← Reddit

Feature Request: Temporal awareness in long-running chats — timestamps per message block

Reddit · Top_Orchid2903 · July 23, 2026
Claude lacks temporal awareness of when messages were sent in long-running conversations, causing it to treat month-old context as current information and reference completed events as ongoing or upcoming. This creates significant problems for users maintaining topic-specific chats for health tracking, trip planning, and project management, where stale information is confidently presented as if still accurate. The proposed solution involves injecting server-side timestamps into Claude's context to enable temporal reasoning and allow the system to flag potentially outdated information.

Detailed Analysis

A feature request circulating in Claude's user community identifies a structural gap in how the assistant handles conversational memory: the absence of temporal metadata within long-running chats. The core complaint is straightforward but consequential. Claude retains the content of past messages but not the timing between them, meaning a health update from June and a follow-up question in July are processed as though they occurred in the same continuous moment. The report documents concrete failure cases — Claude referencing a resolved infant illness as an ongoing concern a month later, and asking about "strap choices" for a family trip that had already concluded weeks earlier. These aren't hallucinations in the traditional sense; the information itself was accurate and drawn from real prior context. The failure is one of temporal reasoning, not factual recall.

This matters because it cuts against the exact use case Anthropic has been pushing users toward: persistent, topic-specific chats and long-term memory features designed to make Claude a durable assistant rather than a stateless tool. As Anthropic and competitors like OpenAI increasingly market memory and cross-session context as flagship capabilities, the underlying assumption is that more accumulated history makes the assistant more useful. This report complicates that assumption — it argues that without a mechanism to weight recency, accumulated history can actively degrade output quality. A model that treats a six-month-old chat as a flat, undated document isn't just failing to improve with more data; it's actively more likely to surface stale or contradicted information the longer a conversation persists. That's a counterintuitive but important dynamic for any AI product betting on long-term memory as a differentiator.

The proposed fix is notably modest in scope: surface existing server-side message timestamps into the model's context, particularly at session boundaries or significant time gaps, rather than requiring any new user-facing behavior or interface change. This is a low-friction, high-leverage suggestion — the data already exists in Anthropic's infrastructure (every message is timestamped for logging and billing purposes regardless), so the ask is essentially about exposing metadata that's already being captured, not building new instrumentation. The request also thoughtfully constrains scope: it explicitly does not want Claude to become obsessively date-conscious or to pepper responses with timestamps, but rather to use temporal context silently, surfacing only when genuinely relevant — e.g., flagging "you mentioned this in June, is it still current?" This kind of scoped, well-reasoned feature request reflects how sophisticated the power-user community around Claude has become, often identifying architectural gaps through sustained real-world usage patterns rather than synthetic testing.

More broadly, this sits within a growing industry conversation about the limits of "memory" as currently implemented across LLM products. Most memory systems, including Claude's, function more like an ever-growing corpus of retrievable facts than like genuine episodic memory with a sense of chronology, causality, or narrative arc. Humans naturally discount old information, recognize when circumstances have likely changed, and ask clarifying questions when uncertain about currency of information — capabilities that are trivial for people but nontrivial to encode in transformer-based context windows without explicit signals. As AI assistants move toward being persistent companions for health tracking, project management, and personal logistics — precisely the long-horizon, high-stakes use cases highlighted in this report — solving temporal grounding will likely become as important as solving factual accuracy, since an assistant confidently wrong about *when* something happened can be just as harmful as one wrong about *what* happened, particularly in domains like pediatric health where staleness could translate into materially bad advice.

Read original article →