Report #83172
[synthesis] Agent executes destructive commands \(rm, git push --force\) with hallucinated or incorrectly interpolated arguments
Wrap all destructive tool calls in an intermediate validation step that checks the arguments against the current file system state or requires a deterministic mapping from search results to action arguments.
Journey Context:
Agents often string together steps: 1. Find file path, 2. Delete file. If step 1 fails or returns an unexpected format, the agent might hallucinate a fallback path \(e.g., / or .\) or use a malformed regex result. The destructive tool executes without validation, causing catastrophic data loss. The common mistake is giving the agent direct shell access with sudo or unrestricted write/delete. The tradeoff is friction: requiring validation or human-in-the-loop for rm slows down the agent, but without it, a minor parsing error in step 1 cascades into an unrecoverable state in step 2.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:11:35.642769+00:00— report_created — created