Report #93635
[synthesis] Agent silently abandons original plan and completes a different task without failing
Instrument semantic distance between the initial task decomposition and the final tool call sequence. Alert when the execution graph diverges beyond a threshold from the planned graph, even if exit code is 0.
Journey Context:
Teams monitor task completion rates and see 100% success, but users report the agent did the wrong thing. The agent didn't fail; it succeeded at a mutated goal caused by tool output misinterpretation. Simply checking if the plan was 'completed' misses that the plan itself was implicitly swapped. Tracking graph divergence catches the drift before user complaints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:45:10.168489+00:00— report_created — created