Cursor Releases Cursor Router: A Request-Level Classifier Delivering Frontier Coding Quality at 30–50% Lower Cost

Cursor has made Cursor Router generally available for Teams and Enterprise plans. The system is a classifier that inspects each request before a model runs, then dispatches it to the model best suited to that specific task. The cursor team reports frontier-quality performance at 60% savings in online A/B tests, and 30–50% savings for early-access enterprise accounts.

The problem it targets is a spend pattern rather than a capability gap. Cursor states that roughly 60% of its developers pick a single model as a daily driver. Routine work therefore gets completed at frontier prices, and AI spend grows faster than output quality. Routing is Cursor’s answer to that mismatch.

What the classifier actually reads

Cursor Router is not a fallback chain or a retry mechanism. It is a classifier trained on 600k+ live requests, evaluated in an online A/B test across millions of live requests, and optimized for user satisfaction (AFC) as its reward signal.

For each request, the router analyzes four inputs: query, context, task complexity, and domain. It combines these with learned knowledge of each model’s behavior. Cursor publishes three routing rules that follow from that classification:

Simple work goes to the most price-efficient models.

UI updates go to the model with the best taste.

Complex, long-horizon problems go to frontier reasoning models.

That third rule carries the weight of the cost argument. The savings do not come from downgrading hard problems. They come from removing routine work from frontier pricing while the difficult tier stays intact.

One implementation detail deserves attention from anyone who has built a router. Cursor Router is cache-aware in both training and evaluation. It is trained on a dataset where routing produces cache misses, and the reported cost savings include the cost of those cache misses. Switching models mid-conversation invalidates prompt cache, and that cost is real. Routers that ignore it overstate their savings.

The classifier was also designed for model churn. Cursor states it can update the router as newer models ship, which matters in a market where the frontier moves monthly.

Interactive Explainer

Inside Cursor Router: classification, tiers and published results

Every figure below is taken from Cursor’s launch post and changelog (July 22, 2026). Values Cursor did not publish are marked as such.

Pick a task — see how the classifier reads it

Step 1 · Signals read before any model runs

▼

Step 2 · Routing tier selected

Cursor publishes three routing rules and does not name a specific model per task type. The tier shown is Cursor’s own published category; the sample tasks are illustrative applications of those three rules. Cursor states the classifier reads query, context, task complexity and domain, combined with what it knows about each model’s behavior.

Auto mode — three points on the cost–intelligence Pareto frontier

Cursor’s description

Published cost per commit (early access measurement)

Linear projection — drag to set monthly commit volume

Volume: 1,000 commits / month

Model / mode$ / commitMonthlyvs Opus 4.8

Cost-per-commit figures are Cursor’s published early-access observations. The projection is straight multiplication of those unit figures — it is arithmetic, not a Cursor forecast, and assumes a constant task mix. Cursor reports GPT-5.6 Sol matched the cost of Intelligence mode but with lower user satisfaction; it did not publish an exact figure for it.

ElementWhat Cursor reports

Training data600k+ live requests

Reward signalUser satisfaction (AFC)

EvaluationOnline A/B test across millions of live requests, not offline evals

Quality metric 1User satisfaction — agent success classified from user responses. Moving to the next feature is a strong positive; correcting the agent is a strong negative.

Quality metric 2Keep rate — how much agent-generated code remains in the codebase over time

Metric track recordBoth metrics used to evaluate every model launch and harness change for the past nine months

Cache handlingCache-aware in training and evaluation. Trained on a dataset where routing causes cache misses; reported savings include cache-miss cost.

Platform scaleCursor routes hundreds of millions of coding requests per week across models and providers

Problem being solved~60% of Cursor developers pick one model as a daily driver, putting routine work on frontier pricing

Cursor’s stated reason for choosing online A/B tests: offline evals are limited by small size, distance from real usage, and the difficulty of reducing success to a rubric — and they omit the extra cache-miss cost incurred when switching models mid-conversation.

Source: cursor.com/blog/router · verified Jul 22, 2026 Built by Marktechpost

Why online A/B tests instead of offline evals

Cursor deliberately avoided offline evals as its primary measurement. Its stated reasoning is that offline evals suffer from small sample size, distance from real-world usage, and the difficulty of reducing success to a rubric. They also omit the cache-miss cost incurred when switching models.

Real routing happens across a conversation, not a single turn. Developers write code, ask follow-ups, hit errors, and continue, often across hundreds of requests in a week. The router must decide both which model to pick and when to switch.

Two quality metrics carry the evaluation:

User satisfaction: agent success classified from user responses. Moving on to the next feature is a strong positive signal. Correcting the agent is a strong negative one.

Keep rate: how much agent-generated code remains in the codebase over time.

Cursor team states it has used both metrics to evaluate every model launch and harness improvement for the past nine months. This is a meaningful credibility marker: the metrics predate the product they are now being used to justify.

Three modes, and the numbers behind them

Auto mode now exposes three optimization settings that move the user along the cost–intelligence Pareto frontier.

Auto Intelligence lands near Fable on user satisfaction at about 60% lower cost for teams. Against Opus 4.8, it lifts satisfaction about 15% at nearly the same cost.

Auto Balance lands above Opus 4.8 on user satisfaction at about 36% lower cost. Against GPT-5.6 Sol, it delivers comparable satisfaction at a lower spend rate.

Cost mode is described as good quality reaching the highest available intelligence while optimizing token spend. Cursor published no A/B quality or cost figures for it.

Cost per request is only part of the picture, so Cursor also measured cost per commit:

Model / modeCost per commit

Auto Balance$4.63

Auto Intelligence$6.76

Opus 4.8$7.34

Fable 5$12.69

GPT-5.6 Sol matched the cost of Intelligence mode but produced lower user satisfaction. Cursor did not publish an exact per-commit figure for it.

Deployment reality and the one hard constraint

Cursor Router ships across desktop, web, iOS, CLI, and the Cursor SDK. It is on by default for Teams plans. Enterprise admins enable it from the dashboard.

The changelog specifies the admin surface: per-team and per-group enablement, restrictions on which optimization modes members can select, a configurable default mode, and model allow and block lists. Soft and hard enforcement options exist for standardizing on Auto. The routed model can be displayed or hidden, and it is hidden by default — teams that want routing transparency must opt in.

Two constraints are important for procurement. First, Grok 4.5 is required as a price-efficient routing option, so the model block list cannot be used to exclude it. Grok 4.5, released July 8, is priced at $2/M input and $6/M output tokens, with a fast variant at $4/M and $18/M. Second, Balance and Intelligence bill at the routed model’s rate, so unit cost varies with each routing decision rather than settling at a flat price.

Key Takeaways

Cursor Router is a per-request classifier trained on 600k+ live requests, optimized for user satisfaction (AFC).

Online A/B tests report frontier-quality output at 60% savings; three early-access enterprise accounts saved 30–50% versus Opus 4.8.

Cost per commit: $4.63 Balance, $6.76 Intelligence, against $7.34 for Opus 4.8 and $12.69 for Fable 5.

Cache-miss cost from model switching is included in the reported savings, not excluded.

Grok 4.5 is a required routing option, and Balance and Intelligence bill at the routed model’s rate.

Sources: Cursor Router launch post, Cursor Router changelog, Grok 4.5 announcement and @cursor_ai on X.

The post Cursor Releases Cursor Router: A Request-Level Classifier Delivering Frontier Coding Quality at 30–50% Lower Cost appeared first on MarkTechPost.