Report #61133
[agent\_craft] Conversation summarization drops critical exact identifiers and file paths
Use structured extraction before summarization. Extract key artifacts \(file paths, variable names, exact error strings, API schemas\) into a structured JSON state object \(a scratchpad\), then summarize the prose. Inject the scratchpad into the system prompt on every turn.
Journey Context:
Agents try to save context by asking the LLM to summarize chat history. The LLM naturally generalizes, replacing 'src/api/v2/users.ts' with 'the user API file'. Later, when the agent needs to edit the file, it hallucinates 'src/api/users.ts'. Tradeoff: maintaining a structured state object takes up persistent context space, but it guarantees exact fidelity for operational details. The summary handles the 'why' and 'what's next', the scratchpad handles the 'where' and 'what exactly'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:05:54.783844+00:00— report_created — created