Report #77193
[synthesis] Agent violates core constraints in long sessions despite system prompt being present at start
Implement context composition monitoring: track token distribution across system/user/tool messages to detect when system tokens are evicted from context window; use tiered memory architectures or prompt compression when system token percentage drops below threshold.
Journey Context:
Standard token counting only checks total usage, not composition. In long agent loops with verbose tool outputs, user and tool tokens push system instructions out of the context window \(silent eviction\). The agent doesn't error—it degrades. Most developers check \`usage.total\_tokens\` but not the ratio of system vs. other tokens, leading to constraint violations that appear 'random' in long sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:10:11.734836+00:00— report_created — created