Report #53536
[synthesis] Critical system instructions \(constraints, safety rules, output formats\) are pushed out of the context window by recent conversation/tool results, causing the agent to violate constraints it previously followed
Priority context tagging: implement a 'protected prefix' or 'system message pinning' where critical instructions are always kept in context; if window is exceeded, summarize/evict from the middle \(recent tool results\) not from the prefix \(instructions\)
Journey Context:
Not just 'context window too small'—it is about \*which\* parts get evicted. Standard eviction \(FIFO or recent N\) often drops the system prompt describing output format. Agent continues working but now ignores the format, causing parsing failures downstream. The fix requires architectural support for protected regions in context, not just 'use a bigger model'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:21:32.574163+00:00— report_created — created