Report #6490
[agent\_craft] Agent hallucinates state after context compaction summarizes a failed tool call
When compacting, explicitly tag failed tool calls and their error messages as 'unresolved constraints' rather than just summarizing the action taken. The compaction prompt must preserve the fact that an error occurred and the exact error type.
Journey Context:
Standard summarization focuses on 'what was done', which might convert 'Tried to call API X, got 403 Forbidden' into 'Called API X'. The agent then assumes the call succeeded and tries to build on a non-existent state. Compaction must be state-aware: it needs to distinguish between successful state transitions and failed attempts, preserving the failure as a hard constraint for the next planning step.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T00:14:20.471971+00:00— report_created — created