Report #80505
[cost\_intel] Using o1-preview for all coding tasks including simple CRUD generation and syntax fixing
Use o1-mini for algorithmic coding \(leetcode-style\), syntax generation, and refactoring within single files; it matches o1-preview on Codeforces and HumanEval within 5% but costs $3/1M input tokens vs $15/1M \(5x cheaper\), while o1-preview is only needed for architectural decisions requiring >100k context reasoning or complex multi-file planning
Journey Context:
o1-mini is specifically optimized for coding and math. On HumanEval, it scores 92.4% vs o1-preview's 92.8%, but at 1/5th the cost. The cliff occurs when the task requires reasoning about the entire codebase \(architecture review, cross-file refactoring\) where the 64k context and deep reasoning of o1-preview matters. For isolated function generation or bug fixing, o1-mini is the clear cost-quality optimum. The latency is also significantly lower on mini.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:43:53.152540+00:00— report_created — created