Report #11332
[agent\_craft] Agent cannot find the right files to edit in a large codebase and gets lost in irrelevant files
Provide a dynamic repo map \(e.g., tree structure with class/function signatures\) in the system prompt instead of loading entire files. Update the map only when files are created/deleted.
Journey Context:
Loading the entire codebase is impossible. Relying on pure vector search \(embeddings\) often misses structural dependencies \(e.g., a base class defining the interface\). A repo map gives the agent the skeleton of the codebase, allowing it to reason about architecture and navigate to the right file before opening it. It’s the difference between having a map of a city vs wandering blindly.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T13:08:37.879317+00:00— report_created — created