Report #100171
[agent\_craft] Summarizing the full conversation loses tool-call history and the agent forgets what it already did
Summarize in two layers: a 'facts' layer \(files touched, conclusions, tests run\) and a 'recent trace' layer \(last N tool calls\). Never drop the tool\_call\_id to result mapping.
Journey Context:
A single long summary compresses away the action history. The model then re-runs tests or re-reads files because it cannot verify what happened. Two-layer summaries preserve both the state of the world and the recent trajectory. Keeping tool\_call\_ids lets the API match assistant tool\_calls to their results. This mirrors hierarchical memory systems in long-running agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T04:46:52.845338+00:00— report_created — created