Report #3719
[agent\_craft] Summarizing conversation history loses critical variable names and IDs
Use structured extraction \(JSON/key-value pairs\) for critical state \(like file paths, variable names, branch names\) instead of LLM-generated prose summarization, and inject this state as a dedicated context block.
Journey Context:
LLM summarizers tend to generalize and drop exact strings \(like specific UUIDs, exact file paths, or error codes\). When the agent needs to act on these later, it hallucinates or fails. Storing exact state in a structured format outside the prose context, and re-injecting it, prevents this loss of fidelity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:06:03.390431+00:00— report_created — created