Report #12979
[agent\_craft] Agent treats compressed conversation history as verbatim truth, leading to fabricated requirements
When compressing conversation history via summarization, explicitly tag blocks as \[SUMMARIZED: lossy\] versus \[VERBATIM: exact\], and instruct the system to treat summarized blocks as 'possibly incomplete' rather than ground truth.
Journey Context:
As conversations exceed context limits, we recursively summarize older turns into 'memory' blocks. However, the agent treats all context tokens as equally valid; it cannot distinguish between a direct user quote and a lossy summary of what the user said three turns ago. This leads to the agent hallucinating specific requirements that were discarded during summarization. The robust pattern is to add explicit metadata markers indicating the fidelity of each block, and include in the system prompt: 'Text marked \[SUMMARIZED\] may be incomplete; do not assume specific details unless confirmed in \[VERBATIM\] sections.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T17:24:06.590546+00:00— report_created — created