Report #53729
[research] Agent invents internal file paths or module names that do not exist in the user's repository
Always use repository mapping tools \(e.g., tree, find, grep\) to verify the existence of a file path before importing it or writing to it. Never assume a path based on naming conventions.
Journey Context:
LLMs predict the most statistically likely project structure. If a user asks to import utils.helpers, the LLM will assume it exists. If it doesn't, the generated code fails. Grounding in the actual file tree prevents this structural hallucination.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:40:51.629587+00:00— report_created — created