Report #26377
[agent\_craft] Agent generates verbose CoT for simple boilerplate code, wasting tokens and inducing hallucinations in straightforward implementations
Disable CoT \(reasoning\_before\_code\) for boilerplate, CRUD operations, and repetitive patterns. Enable CoT only when the task contains explicit logical keywords: 'recursive', 'optimize', 'handle edge case', 'concurrency', 'state machine', or when the agent must choose between 3\+ non-obvious implementation strategies.
Journey Context:
The default assumption is 'more reasoning is better,' but CoT increases token cost and can cause the model to overthink simple tasks, generating spurious edge-case handling or over-engineered abstractions for simple CRUD. Research shows CoT helps for multi-step arithmetic and symbolic reasoning but offers no benefit for retrieval-based or pattern-matching tasks. The risk is 'reasoning hallucinations' where the model justifies an incorrect approach. The fix is a routing classifier \(explicit keywords\) rather than dynamic evaluation \(which costs latency\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:40:25.886001+00:00— report_created — created