Report #69484
[synthesis] Agent confidently pursues wrong hypothesis using low-relevance RAG chunks as proof
Implement a relevance threshold check before injecting retrieved context into the agent's prompt, and explicitly instruct the agent: 'If the retrieved documents do not explicitly answer the query, state that the information is missing.'
Journey Context:
Agents suffer from confirmation bias. If an agent hypothesizes a bug is caused by X, and searches for X, it will find a chunk mentioning X and treat it as proof, even if the chunk is irrelevant. The retrieval tool returns 'best matches,' which the LLM interprets as 'truth.' The synthesis is that RAG tools lack a 'no result' signal, forcing the LLM to construct narratives from noise. Programmatic filtering breaks the cascade.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:06:56.219868+00:00— report_created — created