Cursor Router

Summary

Cursor Router now powers Auto mode, analyzing each request by task type and complexity before sending it to a suitable model. Frontier models handle demanding work, while price-efficient models handle other requests, with Cost, Balance, and Intelligence modes defining different positions on the cost-intelligence pareto frontier. Cost optimizes token spend, Balance targets strong quality, and Intelligence targets frontier quality; Balance and Intelligence bill at the routed model’s rate. Admins can enable routing by team or group, restrict modes, set defaults, allow or block underlying models, use soft or hard enforcement, and choose whether to display the routed model, while the feature is available across desktop, web, iOS, CLI, and the SDK and is on by default for Teams plans.

Takeaways

1. 1

   Cursor Router classifies requests by task type and complexity and sends them to different models, using frontier models for demanding work and price-efficient models for other requests.

2. 2

   Cost, Balance, and Intelligence move across the cost-intelligence pareto frontier. Cost prioritizes token spend, while Balance and Intelligence bill at the routed model’s rate.

3. 3

   Admins can apply routing controls per team or group, including mode restrictions, defaults, underlying-model allow or block lists, routed-model visibility, and soft or hard enforcement of Auto.

FAQ