Report #25169
[cost\_intel] Using Sonnet 3.5 for all code review diffs regardless of complexity
Route diffs <200 lines and single-file changes to Haiku 3.5; reserve Sonnet 3.5 for multi-file architectural changes or >500 line diffs. Implement a classifier or heuristic-based router.
Journey Context:
Haiku 3.5 \(Claude 3.5 Haiku\) matches Sonnet 3.5 on line-level bug detection \(syntax errors, null checks, off-by-one\) at 1/10th cost and 3x lower latency. However, Haiku fails on cross-file dependencies, architectural pattern violations, and security vulnerabilities requiring global context. The optimal architecture is a cascade: Haiku for initial pass, Sonnet only if Haiku confidence is low or diff spans >3 files. Many teams use Sonnet uniformly due to lack of routing infrastructure, wasting 80% of inference budget on tasks Haiku handles identically.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:38:57.039098+00:00— report_created — created