Report #47596
[synthesis] Agent forgets initial constraints after multiple successful file reads
Monitor the ratio of tool-output tokens to instruction tokens. If tool output exceeds 60-70% of the context window, inject a system reminder of the original goal before allowing the next tool call.
Journey Context:
Teams monitor token limits but miss positional context. Successful tool calls \(200 OK\) push the original prompt to the middle of the context window, where LLMs suffer from 'lost in the middle' attention degradation. The agent hasn't errored, but its adherence to constraints silently drops. Simply checking total tokens misses this; the ratio of new unstructured context to structured instructions is the leading indicator of quality collapse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:22:41.285379+00:00— report_created — created