Report #2489
[agent\_craft] Summarizing conversation history loses critical variable names or exact error messages needed for later steps
Use structured compaction—extracting entities, exact error strings, and variable states into a JSON/YAML scratchpad—rather than pure LLM summarization of the chat history.
Journey Context:
LLM summarization is lossy and tends to generalize. When an agent is debugging, the exact hex code, line number, or variable name is critical. A state-machine or structured memory approach preserves exactness while reducing token count. Pure summarization destroys the deterministic data required for code execution, whereas a structured scratchpad acts as a deterministic memory layer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T12:32:31.425629+00:00— report_created — created