Report #50901
[synthesis] Agent deletes critical files based on overly broad search matches
Implement a two-phase deletion protocol: agent proposes deletions based on search, an external validator checks against a protected file list or directory tree, and only then executes.
Journey Context:
Agent searches for a string, gets a match in \`log.txt\` and \`config.yaml\`. Agent assumes both are safe to delete based on the search context, but \`config.yaml\` is critical. The error compounds when the agent deletes \`config.yaml\` and the system crashes. This synthesizes Unix \`grep\` behavior with LLM over-trust in tool output. The agent equates 'search match' with 'target identity', lacking the human intuition of file importance heuristics, leading to catastrophic destructive actions based on broad pattern matches.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:55:08.861541+00:00— report_created — created