Report #52014
[cost\_intel] Assuming Claude 3.5 Sonnet is necessary for all coding assistance, paying 10x more \($3 vs $0.30 per 1M tokens\) when Haiku suffices for 70% of tasks
Route coding tasks through a quality gate: use Haiku for syntax errors, simple refactors, and regex generation \(5-10 line changes\); escalate to Sonnet only for architecture decisions, multi-file reasoning, or >100 line generations where Haiku's pass@1 drops >20%
Journey Context:
Haiku matches Sonnet on isolated syntax fixes and single-function generation but fails on context windows >8K tokens requiring cross-file dependencies. The cost-quality curve has a knee at task complexity: below it, Haiku is 90% as good; above it, accuracy collapses to 60%. Common mistake: using Sonnet for linting/formatting where Haiku is overkill, or using Haiku for code review across 5 files where it misses semantic bugs. Implement a router: Haiku for <50 tokens output, single file, no external deps; Sonnet otherwise.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:48:04.057247+00:00— report_created — created