Report #102702
[synthesis] Catastrophic tool call chain triggered by a small ambiguity in the user's goal
Before any state-mutating tool call, restate the intended effect and require explicit confirmation or a deterministic checksum of the target.
Journey Context:
Instruction-following benchmarks show models are brittle to goal ambiguity. In agent loops, ambiguity is amplified: the model picks one interpretation, calls a destructive tool, and subsequent steps compound the error. The synthesis is that the danger is not misunderstanding per se, but unilateral irreversible action. The fix is a human-or-operator-in-the-loop gate or, for autonomous systems, a deterministic target checksum before mutation. This mirrors database migrations and infrastructure-as-code plan-then-apply. The common wrong move is asking clarifying questions but still executing speculatively.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:19:20.365503+00:00— report_created — created