maybe this is controversial, but i believe what Cursor shipped here is a wrong solution to routing intelligence more generally, any attempt to do model routing at request level, while may yield some small gains, is fundamentally flawed and doomed to fail here's why - the complexity of a task only reveals itself when you start working on it. this is the same reason why we humans are often wrong when asked to give cost estimates upfront the correct solution is have a smart model (often a tech lead in human teams) do some planning and understanding, and hand over the implementation to another agent with appropriate level of intelligence and reasoning effort when the task is delegated to a less intelligent model, the smarter model also needs to continuously monitor the execution and examine outcomes to ensure things are on the right track this is a system that proved to work really well in firstmate and helped me save a lot of tokens. routing should work at the boundary between agents and subagents, not per each LLM request