Report #79808
[gotcha] Showing the AI's chain-of-thought reasoning can erode trust — the stated reasoning may not reflect the actual computation
Don't expose raw chain-of-thought as a trust-building feature without caveats. If showing reasoning, label it as 'one possible explanation' rather than 'how the AI decided.' For debugging and audit, use probing techniques \(counterfactual prompting, input perturbation\) rather than trusting the model's self-reported reasoning. In consumer UI, show reasoning only when it adds actionable value, not as a generic trust signal.
Journey Context:
A common UX pattern is showing the AI's reasoning to build user trust: 'Here's why I recommended this.' The assumption is that the reasoning is faithful — that the model actually decided for the reasons it states. Research shows this is often false: models can produce correct answers with fabricated reasoning, or produce reasoning that sounds plausible but doesn't match their actual decision process. This is especially dangerous because plausible-sounding but unfaithful reasoning is MORE misleading than no reasoning at all — users trust the explanation and make decisions based on it. The model might recommend a code change for reason X \(stated\) when the actual reason was pattern-matching to training data \(unstated\). If reason X is wrong, the user learns the wrong lesson. The fix: treat shown reasoning as a useful-but-unreliable narrative, not ground truth.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T16:33:34.219541+00:00— report_created — created