Report #27387
[cost\_intel] Complex multi-file refactoring routed to cheap models to save token costs
Use frontier models \(Opus, GPT-4\) for planning and complex multi-file refactoring; only delegate isolated, well-defined execution steps to cheaper models.
Journey Context:
Smaller models fail at multi-step reasoning and global state tracking, leading to broken code, hallucinated dependencies, and cascading errors. The cost of a failed agentic loop \(retries, broken builds, human fix time\) vastly exceeds the token savings of using a weaker model. Frontier models are genuinely irreplaceable for the 'architect' role in complex coding tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:21:55.022082+00:00— report_created — created