Report #95623
[agent\_craft] Agent cannot decide which files to load for a cross-cutting feature and either loads nothing or loads the entire codebase
Generate and cache a lightweight repo map \(e.g., files, classes, methods with their signatures and docstrings\) and load this map into context to allow the agent to navigate before loading full files.
Journey Context:
Loading an entire repo is too expensive and exceeds context limits. RAG is too granular. A repo map provides a global view of the codebase structure. The agent uses the map to identify the 2-3 files it needs, then loads the full content of only those files. This drastically reduces token usage while maintaining structural awareness.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:05:14.072548+00:00— report_created — created