Report #29534
[counterintuitive] chain-of-thought prompting always improves accuracy
Apply CoT selectively: use it for multi-step reasoning, math, and logic tasks. Skip it for retrieval, classification, or tasks where the model already has strong intuitive performance. Always benchmark CoT vs. direct prompting for your specific task.
Journey Context:
The original Chain-of-Thought paper demonstrated gains on reasoning benchmarks but also noted that CoT only helps on tasks requiring decomposition and can hurt or show no improvement on tasks where the model already performs well. CoT introduces failure modes: \(1\) the model may rationalize incorrect answers with plausible-sounding reasoning \(unfaithful CoT\), \(2\) longer outputs increase latency and cost, \(3\) the model may overthink simple tasks and introduce errors through unnecessary decomposition. Research by Turpin et al. showed that CoT explanations can be unfaithful—the model's stated reasoning doesn't always reflect its actual computation. For coding agents: don't default to 'think step by step' for every subtask. Use CoT for debugging, architecture decisions, and complex logic; use direct prompting for lookups, formatting, and simple operations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:57:50.687379+00:00— report_created — created