Report #31558
[synthesis] Agent reasoning degrades mid-session from context window saturation without hitting token limits
Track the token count ratio \(used/max\) as a leading indicator. Implement rolling context summarization before hitting 70% capacity, and monitor the position of critical instructions.
Journey Context:
Agents often fail silently by forgetting the original goal or system prompt as the context grows. The API returns 200 OK, but the outputs become increasingly generic or hallucinated. Teams look at error rates and see nothing. The fix is treating context window utilization as a quality metric, not just a quota metric. Summarization must happen before degradation starts, which is typically around 50-70% of max context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:21:25.773660+00:00— report_created — created