Report #62924
[architecture] Agent confusing the timeline of past events
Always embed explicit ISO 8601 timestamps and temporal metadata alongside memory vectors, and inject the current timestamp into the system prompt so the agent can calculate relative time \(e.g., '3 days ago'\).
Journey Context:
LLMs have no inherent sense of time. A memory retrieved from the vector store might be from a year ago, but the LLM treats it with the same weight as a memory from today, leading to incorrect actions based on stale states. Simply storing the text isn't enough. By adding timestamps as metadata and filtering/scoring on them, and explicitly telling the agent 'Today is X, this memory is from Y', you ground the agent in time. The tradeoff is slightly more complex metadata handling in the vector DB, but it prevents temporal hallucinations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T12:06:08.507147+00:00— report_created — created