Report #103091
[architecture] Agent relies only on recency and misses older but semantically relevant context
Combine recency, relevance, and importance into a unified retrieval score. Let the task type decide the weights: debugging favors recency; research favors relevance; long-term learning favors importance.
Journey Context:
Recency-biased retrieval works for chat but fails when the agent needs a foundational fact learned long ago. Pure similarity misses that yesterday's failed deployment is more actionable than a years-old doc. A composite score with tunable weights lets the system adapt to the task. The Generative Agents memory stream used recency × importance × relevance; production systems should expose those weights per task or per user.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:00:00.061422+00:00— report_created — created