Report #22423
[agent\_craft] Summarizing conversation history loses critical variable names and function signatures
Extract and preserve exact identifiers, signatures, and error messages in a structured scratchpad \(e.g., JSON or markdown checklist\) before running compaction/summarization on the narrative history.
Journey Context:
Naive summarization replaces specific code tokens \(e.g., parse\_user\_data\_v2\) with generic terms \('the parsing function'\). When the agent later tries to call this function, it hallucinates the name. Alternatives like keeping full history hit context limits. The tradeoff is a slightly larger context footprint for the scratchpad vs. failed tool calls due to lost exact strings.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:02:57.947403+00:00— report_created — created