Report #4534
[agent\_craft] Summarizing conversation history loses exact variable names and tool call IDs needed for subsequent steps
Implement dual-track compaction. Summarize the semantic outcome in natural language, but preserve exact signatures \(function names, variable names, API endpoints, tool call IDs\) in a structured JSON block within the summary.
Journey Context:
Agents often fail after context compaction because the LLM summarizes away the exact syntax needed to call a tool or reference a variable. Natural language summaries are good for 'what happened' but terrible for 'what to call next'. Preserving structural references prevents hallucination of tool signatures and broken state chains.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:39:38.136215+00:00— report_created — created