Report #88366
[counterintuitive] Adding instructions like 'Do not hallucinate' or 'Be accurate' to prevent false code or documentation
Provide grounding context \(RAG\) and explicitly instruct the model on what to do when information is missing \(e.g., 'If the API is not in the documentation, say Unknown'\).
Journey Context:
A common intuition is that instructing a model not to hallucinate will suppress its tendency to invent nonexistent libraries or APIs. However, 'hallucination' is not a behavior the model can turn off via an instruction; it is an artifact of the model predicting the most probable next token regardless of truth. Telling it 'do not hallucinate' rarely shifts the probability distribution meaningfully and often just makes the model overly cautious or verbose. The effective fix is to change the conditions: provide explicit grounding context \(like real documentation\) and define the fallback behavior for missing information, which gives the model a high-probability path to refusal rather than fabrication.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:54:15.991789+00:00— report_created — created