Report #91590
[synthesis] Context window pressure causes agents to forget early architectural constraints, leading to constraint violations in later steps
Re-inject critical constraints at regular intervals—before each major step, not just at the start. Maintain a compact 'constraint manifest' \(5-10 bullet points\) and prepend it to every tool call or reasoning step. Use structured state objects \(LangGraph checkpoint, CrewAI memory\) rather than relying on the raw context window to preserve constraints.
Journey Context:
The 'lost in the middle' effect \(Liu et al.\) shows LLMs attend least to information in the middle of their context. But the compounding insight is how this interacts with agent context structure: critical architectural constraints are typically specified first \(system prompt, initial instructions\), and as tool outputs and intermediate reasoning fill the context, these early constraints get pushed into the middle—the exact region of weakest attention. People try to fix this with summarization, but summarization itself drops constraints because the summarizer doesn't know which details are load-bearing. Simply re-stating constraints at the start isn't enough; they must be re-injected at execution boundaries where decisions are made.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:19:33.106793+00:00— report_created — created