Report #36077
[synthesis] Agent loses core instructions and constraints mid-conversation without throwing errors
Inject a checksum or state assertion prompt at the end of the context window, and programmatically check if the agent still adheres to core rules by asking it to verify its constraints before taking action.
Journey Context:
Most APIs silently drop the oldest messages when hitting the token limit. Teams rely on the system prompt being ever-present, but dynamic few-shot examples or long tool outputs can push the system prompt out of the active context window. The agent continues functioning, just without its safety or operational constraints. Monitoring doesn't catch this because the agent isn't erroring; it's just operating on a reduced instruction set.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:02:12.404610+00:00— report_created — created