Report #50494
[synthesis] Agent quality degrades on long context runs without hitting context limit errors
Monitor the ratio of high-signal tokens \(user prompt, tool outputs\) to low-signal tokens \(boilerplate, conversational filler, repeated state\) per step. Alert when the ratio drops below a threshold, even if total tokens are well under the context limit.
Journey Context:
Teams monitor context window utilization \(e.g., 90% full\) and assume sub-100% is safe. However, LLM attention mechanisms degrade non-linearly as noise increases. An agent might be at 50% capacity, but if 80% of that is repetitive state-fetching or conversational padding, the 'lost in the middle' effect silently nukes instruction following. The synthesis is that token count is a proxy, but information density per token is the actual leading indicator of attention failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:14:28.965688+00:00— report_created — created