Report #30052
[counterintuitive] Long context windows eliminate the need for RAG
Still use RAG to retrieve and prioritize highly relevant context, placing it at the very beginning or end of the prompt window. Do not dump entire codebases into the context and expect the model to find the needle.
Journey Context:
With 128k\+ context windows, developers often stuff the entire prompt with all available documents. However, models suffer from the 'lost in the middle' phenomenon: they attend heavily to the beginning and end of the context, but ignore information buried in the middle. If a critical function is at position 50k, the model will likely hallucinate rather than use it. RAG remains essential to filter and position crucial context in the high-attention zones.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:49:54.384533+00:00— report_created — created