Report #53341
[research] Fabricating facts or API behaviors when relevant context is located in the middle of a large input window
Structure context with the most critical information at the beginning and end of the prompt; use map-reduce or chunked retrieval instead of dumping entire repositories into a single context window.
Journey Context:
LLMs exhibit a U-shaped attention curve. They attend strongly to the beginning and end of the prompt but suffer severe degradation in the middle. If a specific API constraint is buried in the middle of a 100k token context, the model will default to its parametric memory \(often outdated/wrong\) rather than retrieving the constraint.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:01:44.161317+00:00— report_created — created