TL;DR
The short version
By 2026 the smartest-default is both a quality mistake and a budget mistake. Higher intelligence made one frontier model a better engineer and a worse product manager. And at usage pricing, mis-routing burns real money.
The operator skill is a decision tree keyed to the job, plus a benchmark you run on your own work. Public leaderboard deltas are uneven across task types and do not predict your task mix. The newest twist: open-weight models you host yourself are now a real second source, not a science project.
Built from working reviews by Claire Vo (How I AI), Dan Shipper (Every), and The AI Daily Brief.
What it says
Smartest is not best. Route by job. A model one tier up can be a stronger coder and a weaker PM. The one-word version of the whole idea is "route".
Mis-routing is now a budget mistake, not just a quality one. A top frontier model can run several times the cost per token of a mid-tier one, with higher token burn and tighter rate limits. Usage pricing kills the lazy "top model for everything" habit.
The decision tree. Trivial work to the cheapest model. Routine work to a mid-tier model. Hard non-coding reasoning to a top reasoning model. Multi-hour agentic coding, completeness audits, edge-case hunts, and vision or PDF work to the strongest agentic coder. Prose, specs, PRDs, design, and scoping go to a model with better judgment, not the raw coder.
A cheaper mid-tier model pulls the default down a tier. When a new Sonnet-class model launched at roughly $2 in / $10 out per million against the flagship's $5 / $25 — pitched as "Opus-level tasks at Sonnet-level prices" and aimed squarely at agentic coding — it wasn't just a release, it was a routing event: the cheap-but-good-enough tier moved up, so the default for routine and mid-hard work shifts down and the premium call gets rarer. But route on your own work, not the launch cards. In one blind taste bench that same model topped the automated leaderboard yet had too many broken prototypes and landed bottom of the tester's personal list. New-model pricing pulls the default down; only your own bench tells you which jobs it can actually hold.
Pin your own benchmark. Public benchmark deltas do not predict your task mix. Run an eval on your own codebase and data, not a leaderboard.
A/B before you migrate the fleet. The same release can be a coding gain and a strategy regression at once. Test on your task types before you switch everyone over.
Adviser and executor pairing — now across vendors. Put the expensive model on planning and review, and a cheaper model on execution. This routes intelligence to the layer that needs it and cost to the layer that does not. The split now crosses vendor lines: one practitioner drives a hard task in the smartest model and has it call a cheaper rival model as a sub-agent — the smart model's judgment, the cheap model's fast tokens, without burning the expensive one on high-volume execution.
Cheap per token is not cheap per task. The newest mid-tier agentic model is about 40% cheaper per token than the flagship, but it burns roughly twice the tokens per task — so at full rates a complete run can cost more than the flagship it was meant to undercut. The per-token sticker is not the routing signal; cost per completed task is. The workflow that falls out is an explicit two-tier split: the smartest model as the adviser that plans and judges, the cheap token-hungry one as the fast implementer spawning sub-agents, stacked changes, and adversarial self-review. Use it the way you used the old models and you will have a bad time.
Automate it. The cost fix is a router, not discipline. A lot of token spend comes from people manually picking "the model of the day". An auto-router reads task intent and picks the model, so nobody downshifts by hand for a find-and-replace.
Route-and-panel: the ensemble is a routing strategy too. Fan one prompt out to a panel of models in parallel, have a judge read every response, then have a synthesiser write the grounded final answer. You can hit frontier-level output at a fraction of frontier cost. The insight is not that open models beat the frontier. It is that smart routing beats brute force. And it is no longer theory: once cost and single-vendor sovereignty became joint drivers, both hedges shipped as real deployments — a legal-AI firm ran an open-weight worker model under a frontier advisor at a fraction of the frontier-only cost, and a routing gateway shipped the panel-and-judge pattern as a named product.
Interaction tiers, not just model tiers. A four-model week — OpenAI's full-duplex GPT-Live voice model, xAI's cheap-but-capable Grok 4.5, Cognition's roughly 1,000-token-per-second SWE-1.7, and the new GPT-5.6 Sol — read as one story about routing, not raw intelligence. GPT-Live hands hard reasoning to a background model, so the adviser/executor split shows up even inside a voice interface. The coding version is explicit: run a cheap, fast implementer (Grok 4.5, SWE-1.7) under a smarter orchestrator (Fable 5, GPT-5.6). The economics make it obvious — Grok 4.5 ran an agent benchmark at about $0.34 per task against the flagship's $1.35, on under half the tokens, at near-top scores. Most tasks do not need the flagship; route them to the cheap implementer and reserve the expensive model for judgment. These application-layer models get there by post-training an open base on proprietary product data: closed frontier for exploration, open models for production scale.
Stakes-based routing for non-engineers — and Gemini fell out of the agentic tier. A consumer-facing cut splits work by stakes, not task type: low-stakes chat runs fine on any model, but intensive agentic work has only two serious choices — ChatGPT or Claude, with Gemini "officially out of the rankings" and no leading frontier model. Entry price for the agentic tiers is about $20 a month. The task-type decision tree above is the power-user version; the stakes-based two-way split is the same instinct for everyone else — and a reminder that the frontier agentic set is currently two labs, not the whole leaderboard.
The routing question matured from "best" to "good enough" — and lock-in is the real constraint. A model can top the aggregate intelligence index and set a reasoning-benchmark record at half a rival's price, and still land as a jagged, neurotic daily driver that argues with instructions and stops before the job is done. The synthesis that matters for routing: most knowledge workers do not route across labs — they are locked into one vendor's lineup, and those are their only choices. So judge a release against the models you can actually reach, not the leaderboard. As an upgrade to the prior flagship for a team already inside that ecosystem, it clearly delivers; as a frontier pick for a model omnivore, it is a sidegrade. And the effort dial is part of the route now: the same model can peak at a high thinking setting and get worse at max, looping on self-verification — so reflexively maxing effort is a mis-route too. As routers hide the model, versioned launches may even stop being milestone events within a couple of years.
The pulled-model risk, and the open-weight hedge
Predictability is a driver, not just cost and quality. A closed frontier model is a single point of failure. It can be rate-limited, repriced, or pulled. When a US export-control directive suspended a top model overnight, the named new risk was overbuilding your strategy around one model that can be shut down at random. Routing some workloads to open-weight models you host yourself buys control.
The second source got real: GLM 5.2 is the first open-weight model to survive contact with daily use. Most Chinese open-weight models top a benchmark, then vanish from people's stacks within weeks. GLM 5.2 is behaving differently — respected builders, not anonymous hype accounts, say it holds up in real work, and Vercel's CEO called himself "almost shocked at how good" it is at coding. One third-party design arena even ranked it first on website design (while putting it behind the flagship on game dev, data viz, 3D, and UI components — a narrow win, not a sweep). The signal worth routing on is the source, not the score.
Open weight is no longer the same as cheap — and "run it locally" is a distraction for almost everyone. Running GLM 5.2 well reportedly needs roughly eight high-end GPUs, and it burns far more output tokens, so even at lower per-token rates you wait longer and may pay more than a hosted frontier model. The right route for nearly all teams is a router or an open-source harness, not a GPU rig. Self-hosting only earns its keep when you genuinely cannot tolerate a model being repriced or pulled.
What it means to be 3 or 6 months behind the state of the art now has a lot more viable use cases than what it meant to be 3 or 6 months behind a year ago.
Nathaniel Whittemore, The AI Daily Brief
The operator move is optionality, not migration. Do not rip out your core subscriptions. But give part of the org a sandbox and a budget to experiment, because as the trailing edge of capability covers more real work, the cost, speed, and quality tradeoffs worth testing widen. Routing maturity is a portfolio decision, not a single swap.
A hands-on test confirms the route — and names the weak spot: React. One practitioner wired GLM 5.2 into Cursor and Claude Code through a router and ran three real tasks on her own codebase: explore-and-explain, redesign a marketing hero, and a 45-minute autonomous "pull the errors, build a fix plan" job. Comprehension and design were strong — it matched the existing design system and even nailed the brand color other models miss — but it stalled repeatedly on TypeScript and JSX. "I don't think it can write React, which is 98% of what I do with these models." The routing rule that falls out: send comprehension, design-system work, and long autonomous backend jobs to the cheap open-weight model, and keep React and TypeScript generation on a frontier model. The economics that make the split worth it: about $3.36 for roughly six million tokens, routed through a gateway — so "as long as the model has good taste, I don't need to be fancy and use the most expensive one."
The cost-routing thesis just got its corporate-scale proof. Coinbase rewired its stack to default engineers to open-weight models through an internal gateway and cut its AI bill roughly in half while token usage grew. Ninety-one percent of its engineers never hit a usage cap — so the spend problem was the default model, not the people. That inverts the usual fix: you do not ration the humans, you change what they route to by default. It is the usage-pricing lesson at company scale, and unlike the single-practitioner checks above, the bill-halving was corroborated by outside coverage. A cheaper frontier tier landed the same week — a new top-lab model at roughly half the price of the incumbent flagship — so the spread of options to route across is widening, not collapsing.
Regulatory risk is becoming a fourth routing dimension. Routers already trade off cost, latency, and quality per request. In a grayer legal environment — a capability ban on one model here, a possible export restriction on another there — a router picks up a governance job: choosing models by regulatory exposure, not just capability. If some models become restricted by jurisdiction or user, the routing layer is where "which models am I even allowed to call for this request?" gets enforced. The router stops being pure cost-optimization and becomes a compliance control point.
