Why is a long context not reliable long-term memory?
Test window size, positions and retrieval separately.
Content revision 4 · 2026-10-24
I04 · Revision 1 · 2026-10-21
- Capacity: how much fits
- Retrieval: where is evidence
- Reasoning: is it used correctly
The bottleneck
Accepting more tokens establishes an input capacity, not reliable use of every fact. Lost in the Middle found positional sensitivity in its tested models and retrieval/QA tasks, with information in the middle sometimes used less effectively.
The mechanism
RoPE rotates queries and keys so their dot products encode relative position. Extending windows also requires training-length coverage, positional extrapolation or scaling and validation. It does not solve all retrieval interference. Measure capacity, retrieval and reasoning separately.
dense attention work ∝ T²; standard KV payload ∝ T
Examples and evidence
Teaching protocol: place the same evidence at the beginning, middle and end, adding similar distractors. Compare citation accuracy and answer quality while holding question and length fixed. Historical results are not a verdict on every current model.
New constraints
Long inputs increase prefill work and KV memory. Compression, retrieval and summaries may omit crucial details. Systems need evidence localization, citation checks and task-level evaluation rather than selection by maximum window size alone.
Primary sources
- RoFormer: Enhanced Transformer with Rotary Position Embedding · 2021-04-20 · Checked 2026-10-21
- Lost in the Middle: How Language Models Use Long Contexts · 2023-07-06 · Checked 2026-10-21
Manual browser reading records and interactive calculators are available with JavaScript.
Keep exploring
I01 · Why does KV cache grow with context and concurrency?
S03 · Why can FlashAttention be faster with the same formula?