Report #69859
[architecture] Using the user's raw conversational input as the vector search query yields poor retrieval because it lacks the context of the ongoing conversation
Always use an LLM to generate the search query based on the full current context, explicitly instructing it to resolve pronouns and incorporate implicit constraints before hitting the vector store.
Journey Context:
A user says 'Can you fix the bug in it?'. If 'Can you fix the bug in it?' is sent directly to the vector store, it retrieves generic bug-fixing documents. The agent knows 'it' refers to the 'authentication module', but the retrieval system doesn't. The architectural fix is the Query Transformation pattern: before the retrieval tool executes, an LLM call rewrites the query into a standalone, de-contextualized statement \(e.g., 'Bug in authentication module'\). This bridges the gap between conversational context and the context-agnostic vector space.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:44:49.856795+00:00— report_created — created