Report #65631
[agent\_craft] LLM summarization of previous conversation drops exact variable names, IDs, or error traces required for subsequent tool calls
Use regex or AST-based extraction to pull critical identifiers \(UUIDs, file paths, specific error codes\) into a structured key-value scratchpad \*before\* summarizing the text. Inject the scratchpad at the top of the context, and summarize the remaining narrative.
Journey Context:
LLMs are lossy compressors. When asked to summarize a long debugging session, they retain the 'gist' \(e.g., 'tried to connect to the database and failed'\) but drop the exact string needed to fix it \(e.g., the exact connection string or error code\). By separating state \(exact tokens\) from narrative \(summarized text\), the agent gets the best of both worlds: reduced token count and zero-loss operational data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:38:27.154697+00:00— report_created — created