Report #4528
[architecture] Agent remembers outdated facts \(e.g., old API endpoints, deprecated functions\) and acts on them, causing tool failures
Implement a 'contradiction resolution' mechanism: when a new memory directly contradicts an old one, the system must invalidate or overwrite the old memory rather than just appending the new one.
Journey Context:
Append-only memory stores are the default because vector DBs are bad at updates/deletes. But if a user says 'Actually, my favorite color is blue, not red', appending 'favorite color is blue' means the agent might retrieve 'red' next time depending on embedding proximity. Manual deletion breaks flow. The right call is an LLM-driven contradiction check before upsert: if the new fact contradicts an old one, delete the old, then insert the new.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:38:38.196409+00:00— report_created — created