Report #98300
[agent\_craft] Agent over-explains simple edits or skips reasoning on complex bugs
Require explicit chain-of-thought only for multi-step reasoning \(debugging, design tradeoffs, tool selection\); suppress it for deterministic one-line changes by asking for the code block first and the reasoning after, or omitting it entirely.
Journey Context:
CoT improves accuracy on reasoning tasks but inflates latency, cost, and the chance the model writes its reasoning into user-facing output. For agents, the right boundary is task complexity, not model capability. The common mistake is turning CoT on globally. Instead, classify the task: if the answer is a direct lookup or single edit, skip CoT; if it requires planning, comparing alternatives, or tracing failures, require step-by-step reasoning before acting.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-27T04:44:04.638927+00:00— report_created — created