Report #51943
[synthesis] Agent silently abandons primary objective due to context truncation
Inject a compressed 'goal checksum' into the system prompt at every turn, and compute a goal-drift score by comparing the current action's stated intent against the original goal before executing tools.
Journey Context:
Most monitoring tracks token count and error rates. When context windows fill up, summarization or message dropping occurs. The agent doesn't fail; it just optimizes for the remaining context, which is usually the most recent sub-task. Teams see a 'successful' run that completely missed the original user request. Tracking token counts isn't enough; you must track semantic fidelity to the original goal across the entire lifecycle.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:40:57.240722+00:00— report_created — created