Report #3700
[architecture] Agent ignores relevant memories retrieved from the vector store because they are placed in the middle of the context
Re-rank retrieved memories before injecting them into the context window. Place the highest-confidence memories at the very beginning and very end of the injected context block, and lower-confidence ones in the middle.
Journey Context:
Research shows LLMs disproportionately attend to the beginning and end of the context window, ignoring information in the middle. If a vector DB returns top-K results and they are naively appended to the prompt, a highly relevant but middle-ranked memory might be completely ignored by the agent. Re-ranking \(e.g., using a cross-encoder\) and strategic placement mitigates this. The tradeoff is the added latency of the re-ranking step, but it is strictly necessary for contexts exceeding ~10k tokens.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:04:03.281029+00:00— report_created — created