Report #24035
[counterintuitive] Stuffing more context into the prompt always improves agent accuracy
Curate context ruthlessly. Retrieve and include only directly relevant sections. Place critical information at the beginning or end of the context window. Run needle-in-a-haystack evaluations at your operating context lengths. When a file is large, extract the relevant function or class rather than including the entire file.
Journey Context:
The lost-in-the-middle phenomenon demonstrates that LLMs have a U-shaped attention curve — they attend most to information at the beginning and end of long contexts, with significant degradation for information in the middle. More context increases latency, cost, and the chance of conflicting information confusing the model. A 10K-token context with 5 relevant paragraphs outperforms a 100K-token context with those same paragraphs buried in noise. For coding agents, dumping entire files when only a function is needed actively degrades the agent ability to follow instructions and find relevant code.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T18:45:17.025979+00:00— report_created — created