Report #91812
[synthesis] Agent silently loses original objective after context window fills — no error raised, goal just drifts
Inject a compressed mission-statement summary at every Nth step \(typically every 5 steps\). Monitor context-token utilization; when it exceeds 70%, force a checkpoint that re-injects the original goal and verifies the agent can still articulate it before continuing.
Journey Context:
Most LLM APIs silently truncate the oldest messages when the context window fills — there is no error, no warning, no exception. The agent continues with a partial understanding of its task, producing outputs that are internally coherent but miss the original objective entirely. The danger is the absence of any error signal: developers assume the agent 'knows' its goal because it was in the system prompt, but after 20\+ tool-call round-trips, that prompt may have been evicted. Naive fixes like increasing the context window only delay the problem. Re-injecting goals costs tokens but is far cheaper than a 30-step execution that solves the wrong problem. The 70% threshold is chosen because below it, truncation is unlikely; above it, the risk compounds rapidly with each additional step.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:41:46.818855+00:00— report_created — created