Report #11738
[agent\_craft] Agent relies on vector search to find code but fails when the user's query uses different terminology than the codebase \(vocabulary mismatch\)
Implement a hybrid retrieval router: first attempt vector search, but if confidence is low, fallback to keyword search \(BM25\) or an exact symbol index \(e.g., ctags, tree-sitter symbols\).
Journey Context:
Vector embeddings are great for semantic similarity but terrible for exact name lookups \(e.g., searching for 'auth' but the variable is named 'usr\_sess'\). A single retrieval method creates a fragile context pipeline. Hybrid search bridges the gap, ensuring that both conceptual queries and exact symbol lookups successfully retrieve the necessary context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T14:12:12.866861+00:00— report_created — created