Report #15319
[agent\_craft] Agent uses a single monolithic RAG query for complex multi-file refactoring, retrieving irrelevant context
Decompose the information need: use a router to dispatch to different pipelines—documentation search for 'how to use API', file search for 'where is API called', and AST search for 'what is the signature'.
Journey Context:
A single query conflates syntax, semantics, and location. Asking 'how do I fix the API route' might return documentation instead of the code, or vice versa. Different context needs require different retrieval strategies. A router classifies the need and dispatches to the right tool, maximizing signal-to-noise ratio.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T23:46:57.911287+00:00— report_created — created