Qwen 3.8 Max Burned a 5-Hour Token Quota on One Flutter Task That a Free Model Finished in 3 Minutes
Benchmark scores that don't test your actual stack and workflow are a costly proxy. A model can rank near the top on LiveBench coding yet be economically unusable for Flutter work because its verbosity burns through paid quotas before finishing the job.
A straightforward Flutter integration job — wiring three finished modules into a main workflow — consumed an entire 5-hour token plan on Qwen 3.8 max without completing. The same task finished in 3 minutes and 17 seconds using opencode's free model. The root cause was excessive verbosity: the model's reasoning chains grew so long across rounds that token limits were exhausted before the work was done.
LiveBench scores place Qwen 3.8 max just below Claude and GPT-5.6 in overall and coding capability, but those benchmarks test Python and web tasks, not Flutter. The developer's actual workflow — using a top model to decompose requirements, then a mid-range model to build each feature — doesn't map cleanly to any single benchmark dimension. Cost-effectiveness rankings confirm the coding inefficiency: the model's strength lies in logic and data processing, not programming.
A practical takeaway emerges: the remaining token quota handled typo fixes, formatting, and GitHub publishing for the very article describing the failure, reinforcing that Qwen 3.8 max performs better on non-coding chores. Low-tier paid plans that can't survive a single long conversation hold no practical value when competitors offer generous free tiers.
Benchmark-to-project mismatch isn't just about language; it's about workflow. A model optimized for single-shot code generation may fail badly in multi-turn, context-accumulating agentic loops.
Verbosity is a hidden cost driver that benchmark scores don't capture. A model can be both capable and economically non-viable if its reasoning style inflates token consumption per task.
The fact that the same model handled text-editing chores efficiently but failed at coding suggests the token-burn problem is specific to how it approaches programming tasks, not a universal trait.