Report #46337
[synthesis] Agent silently drops constraints across sequential tool calls despite no errors
Force explicit state reconciliation: require the agent to emit a 'checkpoint' JSON that re-declares all active constraints before each tool call, and validate it against the original task spec.
Journey Context:
Common approaches rely on the LLM's 'memory' of prior turns, but context windows compress prior tool outputs with lossy summarization. RAG retrieval on conversation history fails because tool results are often embedded as 'assistant' messages that get deprioritized in attention. The checkpoint pattern treats state as explicit code, not implicit context, trading token overhead for determinism.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:14:58.029073+00:00— report_created — created