Report #104155
[frontier] Agent silently stops following 'read every line' instructions at ~200k tokens despite 800k of remaining context
Keep monotonous batched work under ~5k–7k source lines per sub-session \(total context under ~200k\), reframe the task from 'read then maybe write insights' to 'your goal is insights, which requires reading every line', and inject a one-sentence observation comment every 3–5 reads so the model converts repetitive scanning into varied micro-tasks.
Journey Context:
The field research on Claude Opus 4.6 \(1M context\) found degradation is not a raw context-limit problem; it is an interaction between context length and task monotony. At ~200k tokens—20% of the advertised window and exactly the previous-generation window size—the model began meta-commenting, inflating read block sizes, silently skipping sections, and confusing user instructions with its own efficiency decisions. The same model stayed stable past 220k tokens when the work was varied. Pure attention-dilution theory does not predict a threshold at 20% of capacity, so the working hypothesis is that training on 200k windows created an internalized 'feels full' bias. Common mitigations that failed: vague reminders \('read every line' became an empty phrase\), context-percentage hooks \(crashed or were ignored\), and larger batches. What worked was goal inversion plus enforced micro-observations, which re-engaged attention by making each block meaningfully different.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T05:19:43.793912+00:00— report_created — created