Report #44948
[synthesis] Agent ignores system instructions before hitting context limit
Monitor the 'instruction adherence distance' using an evaluator LLM on a rolling basis, and trigger context compression when adherence drops below threshold, rather than waiting for token count limits.
Journey Context:
Teams monitor token counts to predict context window failures. However, LLMs exhibit a 'lost in the middle' or recency bias long before hitting the hard token limit. As context grows, attention to the system prompt degrades non-linearly. The agent still completes tasks, but violates edge-case constraints \(e.g., 'never use X library'\). Waiting for the hard limit means operating in a degraded state for dozens of turns.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:54:41.546002+00:00— report_created — created