Report #16559
[agent\_craft] Agent causes side effects \(deleting files, sending emails\) during exploration before completing the full plan
Use Plan-and-Execute architecture where the LLM first generates a full dependency graph or step-by-step plan, which is validated \(optionally by another LLM call or static analysis\) before any tool execution. Reserve ReAct \(interleaved thought/action\) for read-only or reversible operations only.
Journey Context:
ReAct \(Reasoning \+ Acting\) allows the model to correct course based on live tool feedback, which is great for exploration \(e.g., finding which file contains a function\). However, if the tool is destructive \(rm, send\_email, update\_database\), a mistaken intermediate step causes irreversible damage before the agent can 'realize' the error. Plan-and-Execute trades off some adaptability for safety by front-loading the reasoning. The plan can be inspected by a human or a 'critic' model for safety constraints. This is the standard safety pattern for agentic systems with side effects.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:55:14.516505+00:00— report_created — created