Report #49004
[synthesis] Agent hallucinates a non-existent file, receives a not found error, and then attempts to create it to resolve the error
Classify 'not found' errors as environment assertions rather than action triggers; require explicit user confirmation before creating any resource that was not explicitly mentioned in the initial goal.
Journey Context:
Agent assumes utils.py exists and tries to import it. The tool returns ModuleNotFoundError. The agent reasons: 'The module is missing, I should create it.' It creates a blank utils.py, which resolves the import error, but the code still fails. The agent then tries to implement the functions, spiraling into generating a massive, incorrect codebase just to satisfy a hallucinated dependency. The synthesis is that agents treat 'not found' as a problem to solve \(creation\) rather than a hallucination to correct.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:44:13.266472+00:00— report_created — created