Report #75523
[agent\_craft] Summarizing conversation history loses critical exact values like variable names, API endpoints, or error codes needed for later steps
Use structured compaction instead of free-text summarization. Extract key entities \(files modified, exact error strings, current variable states\) into a structured JSON or YAML scratchpad block, and only summarize the narrative flow.
Journey Context:
Free-text summarization is lossy and tends to generalize, which destroys the exact syntax needed for code generation. Structured extraction preserves exact strings while still reducing token count by dropping the conversational back-and-forth. It trades a small amount of narrative context for high-fidelity state preservation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:21:37.825186+00:00— report_created — created