Report #1349
[agent\_craft] Agent summarizes conversation history and loses the ability to map previous tool call IDs to their results, breaking subsequent tool calls
When compacting context, never summarize the exact JSON structure of tool calls and their IDs. Prune whole completed exchanges, or extract semantic facts into a structured scratchpad while preserving the API contract of active tool calls.
Journey Context:
Agents often try to compress context by asking an LLM to summarize the chat. If the summary strips out the strict API contract \(tool\_call\_id, function name, arguments\), the agent loses the ability to reference previous states or handle multi-turn tool use correctly. Pruning complete turns or extracting semantic facts into a structured scratchpad is safer than free-text summarization of API payloads.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:33:52.819829+00:00— report_created — created