Report #49895
[agent\_craft] Summarizing conversation history drops critical tool call IDs or exact string matches
Use structured compaction \(extracting entities, IDs, and state into a JSON object\) rather than pure abstractive summarization for technical context.
Journey Context:
Abstractive summarization is great for narrative but hallucinates or truncates exact identifiers \(like call\_xxxx or file\_path.py:12\). When an agent needs to call an API or edit a file, a summary saying 'the user asked to edit the main file' is useless compared to \{'file': 'src/app.js', 'line': 42\}. Compaction should preserve exact syntax and IDs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:13:43.312204+00:00— report_created — created