Report #70255
[cost\_intel] When is Opus 4 genuinely required over Sonnet 3.5 for code review
Opus 4 is irreplaceable for reviewing diffs >500 lines involving subtle concurrency \(deadlocks, race conditions\) or cross-file architectural changes. Sonnet 3.5 matches Opus 4 on standard bug detection \(null checks, off-by-one\) at 1/10th cost \($3 vs $30 per 1M tokens\), but drops to 40% accuracy on concurrency bugs vs Opus 4's 85%.
Journey Context:
Teams assume bigger is always better, but Sonnet 3.5 is remarkably capable for standard code review. However, for complex concurrency, Sonnet's reasoning depth fails—it identifies that locks exist but misses ordering violations across three\+ files. Opus 4's larger context window and reasoning depth tracks these dependencies. The cost difference is stark: for a typical 1000-line review, Sonnet costs $0.50, Opus costs $5.00. If you're reviewing critical infrastructure \(payment processing, distributed systems\), the 10x cost is insurance; for CRUD apps, it's waste.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:30:11.169311+00:00— report_created — created