Report #73519
[architecture] Agent outputs conflicting or outdated information because old instructions or facts are still in the context window
Apply explicit decay weights to memory retrieval and use a 'scratchpad' pattern where the context window is actively rewritten/overwritten by the agent, rather than purely appended to.
Journey Context:
A common mistake is treating the context window as an append-only log. As the context grows, older, superseded facts remain, leading the LLM to hallucinate or contradict itself by mixing old and new state. By giving the agent write/delete tools over its own working memory \(scratchpad\) and applying time-decay scoring in vector retrieval, you ensure stale facts are pruned or overwritten, keeping the active context highly relevant.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T05:59:39.194046+00:00— report_created — created