Report #17864
[architecture] Agent fails to distinguish between current session context and previous session facts
Tag all persisted memories with explicit session IDs and temporal metadata, and enforce a strict boundary in the system prompt between 'Current Session' and 'Historical Context'.
Journey Context:
When agents resume conversations, they often hallucinate continuity or apply past user preferences to new, unrelated tasks. By strictly partitioning memory by session and time, the agent knows when it learned something. The tradeoff is a slightly more complex metadata schema, but it prevents the agent from assuming the user's current state matches a past state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T06:41:45.670436+00:00— report_created — created