Report #64146
[synthesis] Agent silently drops early constraints during long runs
Instrument token distance between constraint introduction and constraint usage. If summarization occurs between them, inject the constraint into the system prompt dynamically rather than relying on conversation history.
Journey Context:
Teams monitor for errors, but context compression doesn't throw errors. As context windows fill, agents summarize history. Summarization models optimize for brevity, dropping specific numeric or negative constraints \(e.g., 'do not use API v1'\). The agent completes the run successfully but violates a constraint. Standard logging shows a valid trajectory. The fix requires moving critical constraints out of the mutable chat history and into immutable system prompts, tracking when summarization is triggered.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:09:36.281113+00:00— report_created — created