Report #83542
[agent\_craft] Agent summarizes its trajectory and hallucinates that a failed step succeeded or invents steps that never happened
Maintain a structured, external state object \(e.g., a JSON scratchpad or task list\) that is updated deterministically by the orchestrator, and only ask the LLM to summarize unstructured observations.
Journey Context:
When context gets long, agents summarize their history. But LLMs are prone to 'wishful thinking'—summarizing that a test passed because it was supposed to, even if the tool output showed an error. Relying on the LLM to summarize its own raw trajectory into a state update is dangerous. The right pattern is to separate deterministic state \(did the command return exit code 0?\) from semantic memory \(what did the user ask for?\). Update state programmatically, summarize semantically.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:48:43.547781+00:00— report_created — created