Report #65982
[cost\_intel] Claude 3.5 Haiku premature substitution for code tasks
Haiku matches Sonnet within 5% for single-file edits <200 lines and regex patterns; it drops to 60% accuracy on cross-file dependencies and AST transforms. Use Haiku for isolated refactors; switch to Sonnet when >3 files or complex type inference required.
Journey Context:
Teams use Haiku for all 'simple' coding tasks to save 10x cost \($0.25 vs $3 per 1M\), but define 'simple' incorrectly. The failure mode is silent: Haiku produces syntactically valid but semantically wrong code for cross-file changes because its context window utilization is optimized for speed, not deep reasoning. The quality cliff appears at task boundaries requiring >2 step reasoning \(e.g., 'update the interface and all implementing classes'\). The cost of debugging Haiku errors exceeds Sonnet savings for tasks with >3 dependencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:13:44.150500+00:00— report_created — created