Report #6084
[architecture] Agent retrieves two conflicting memories and hallucinates or freezes
When retrieving memories, fetch the top-K results with a lower similarity threshold. If multiple memories with high similarity but contradictory semantics are returned, inject both into the prompt and force the LLM to arbitrate using recency or source authority metadata.
Journey Context:
Users change their minds \(e.g., 'I prefer Python' then later 'I actually prefer Rust'\). If the agent retrieves both, it might average them out or use the wrong one. Explicit arbitration in the prompt is required. The tradeoff is consuming context window space with conflicting data, but it prevents the agent from making false assumptions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:09:10.938508+00:00— report_created — created