Cursor Router: When 60% of Developers Use One Model, the IDE Starts Routing for Them
Cursor opened its July 22 announcement of Cursor Router with a revealing number: roughly 60% of developers using Cursor choose one model as their daily driver. That means typo fixes, field renames, unit tests, UI work, and long-horizon architecture problems may all go through the same model. Routine work gets billed at frontier prices even when frontier capability adds little to the result. I do not think this is primarily a user-selection problem. It is a supply-side mismatch. The model pool keeps expanding, but developers are still expected to schedule it manually, one request at a time. Cursor Router moves that decision into the IDE, before any model runs. ...