Report #95383
[cost\_intel] When does Claude 3.5 Haiku match Sonnet for code review quality
Use Haiku for syntax/linting errors \(catches 95% at 1/5th cost\), reserve Sonnet for architectural refactoring suggestions
Journey Context:
Teams assume Haiku is for 'simple' tasks but the quality cliff is sharp at semantic reasoning. Haiku catches missing imports and syntax errors reliably, but hallucinates refactoring patterns that cross multiple files. Sonnet is required when suggesting class hierarchy changes or analyzing cross-file dependencies. The cost difference is 5x, so routing by task type yields 60% cost savings on large codebases without quality loss on critical logic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:40:39.159898+00:00— report_created — created