Report #93714
[cost\_intel] Claude 3.5 Haiku vs Sonnet for automated code review tier selection
Use Claude 3.5 Haiku for pre-commit syntax/bug detection \(unreachable code, type errors, style violations\) at 1/8th cost of Sonnet \($0.80 vs $6/1M tokens\) with equivalent precision. Mandatory upgrade to Sonnet for architectural reviews: circular dependency detection, abstraction layer violations, and cross-file refactoring suggestions. Haiku fails on architectural tasks due to 200k context window \(vs 200k for Sonnet but with poorer long-context recall\) and inability to track implicit dependencies across >5 files.
Journey Context:
Teams run entire CI/CD on Sonnet costing thousands monthly, but Haiku catches 95% of simple bugs at 1/8th price. The mistake: using Haiku for 'simple' security reviews that require tracing data flow across microservices—it misses 30% of SQL injection paths Sonnet catches. The signature: Haiku excels on localized pattern matching \(regex-like logic\), Sonnet on global graph reasoning. Implementation: parallel tier—Haiku for fast feedback \(<1s\), Sonnet for deep analysis on Haiku-cleaned diffs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:53:08.419348+00:00— report_created — created