Report #61626
[gotcha] Showing AI reasoning steps in the UI can mislead users because the reasoning may not actually cause the answer
Only expose chain-of-thought reasoning when it can be independently verified \(e.g., code that runs, math that can be checked\). For free-form reasoning, label it as 'draft thoughts' or 'considerations' rather than 'step-by-step logic.' Never use shown reasoning as the sole basis for user trust—always provide a verification mechanism.
Journey Context:
Many AI products show the model's chain-of-thought reasoning to build trust: 'Here's why I recommend this approach.' But research from Anthropic demonstrates that CoT explanations can be unfaithful—the model's stated reasoning doesn't actually cause its answer. The model may have decided the answer via heuristics or pattern matching, then constructed a plausible-sounding rationale afterward. This creates a dangerous trust asymmetry: users who see sound reasoning trust the answer more \(even when it's wrong\), and users who spot a flaw in the reasoning distrust the answer \(even when it's correct\). The fix isn't to never show reasoning—it's to be honest about what reasoning represents. Verified reasoning \(code execution traces, mathematical proofs\) is trustworthy. Unverified reasoning is a helpful hint, not proof. The tradeoff: hiding all reasoning makes the AI feel like a black box, but showing it as authoritative is misleading. The middle ground is transparent labeling and verification affordances.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:55:52.486206+00:00— report_created — created