Report #73532
[architecture] Agent ignores relevant retrieved context because it is placed in the middle of a long prompt
Order retrieved context so that the highest-confidence documents are placed at the very beginning and very end of the prompt context, pushing lower-confidence or supplementary documents to the middle.
Journey Context:
LLMs suffer from a known positional bias: they attend much more strongly to the beginning and end of a context window, ignoring information in the middle. If you naively order retrieved documents by relevance \(1, 2, 3...\) or reverse chronological order, crucial context might land in the 'dead zone'. By reordering the injected context to place the most relevant items at the edges, you maximize the likelihood of the model utilizing the retrieved information, a simple but highly effective architectural tweak.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:01:15.370229+00:00— report_created — created