Report #3110
[agent\_craft] Model invents file paths, imports, or conventions because it lost the project map
Keep a living project map at the top of context: file tree, dependency graph, build/test commands, and project-specific conventions. Refresh it when files change.
Journey Context:
Agents often skip directory listing and guess paths. A map is cheap tokens relative to the cost of a wrong edit. It should be structured, not prose, and regenerated after file moves. The common mistake is to rely on retrieval for everything; retrieval fails when the query does not match filenames. The map gives global affordance. For coding, invariant metadata should be pinned at the start so prompt caches stay valid and the model never navigates blind.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T15:31:43.922267+00:00— report_created — created