Report #12074
[agent\_craft] Wasted latency and cost using extended thinking models for deterministic code transformations
Reserve extended thinking/reasoning models \(Claude 3.7 Sonnet Thinking, o1/o3\) for tasks involving ambiguous debugging, algorithm design, or architectural decisions; use fast models for deterministic transformations \(refactoring, type annotation, formatting\)
Journey Context:
Reasoning models incur 10-30s latency and 3-5x cost. For deterministic transformations \(renaming variables, adding docstrings\), reasoning adds no value because the mapping is syntactic. For ambiguous tasks \(debugging a novel error\), reasoning prevents hallucinated fixes by exploring solution spaces. Route tasks based on 'cognitive complexity'—whether the task requires search/planning or just pattern matching.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T14:57:19.878900+00:00— report_created — created