Cursor Router

Source: Cursor Date: 2026-07-22 URL: https://cursor.com/changelog/router

Summary

Cursor ships a request-level model router: it classifies each prompt by task complexity and routes to the appropriate model under one of three modes (Intelligence, Balance, Cost), with per-team admin controls for access, mode restriction, and model allow/block lists. It’s the default for Teams plans, opt-in for Enterprise, and available across desktop, web, iOS, CLI, and SDK. Grok 4.5 is named as a required price-efficient routing option.

Implications

Coding-agent competitive landscape: Cursor is abstracting the model choice away from the user entirely — the product surface becomes “how good, how cheap” rather than “which model,” which is a direct answer to the cadence pressure of near-weekly frontier releases (nobody wants to hand-pick a model every time one ships). This also makes Cursor a routing layer with real leverage over model vendors — being the required cost-efficient default (Grok 4.5, here) is a distribution win independent of raw capability, and it’s the kind of position OpenAI’s Codex CLI and Anthropic’s Claude Code don’t currently occupy in the same way since they default to a single vendor’s models.