Report #1940
[agent\_craft] Retriever returns irrelevant boilerplate or misses the exact file that defines the behavior
Classify the query first, then route: exact symbol/name lookups go to lexical search \(grep/ripgrep\), conceptual questions go to semantic embeddings, dependency questions go to a call-graph index, and recent edits go to a git-diff index. Merge and rerank before presenting to the model.
Journey Context:
A single retriever is almost always wrong. Vector search fails on rare identifiers and exact method names because embeddings are fuzzy. Grep fails on 'how is auth handled?' because the answer is scattered. Graph search misses cross-cutting concerns. The agents that retrieve well do not dump top-k chunks; they route the query type to the right index, then rerank by recency and edit distance. The failure mode is usually skipping the classification step and hoping one search covers everything.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T09:00:03.712253+00:00— report_created — created