alt Hacker NewsOur experience has been the direct opposite. The way to get the most out of cursor was to leave it on auto - we saw it average around 3.9 cents per request under the old contract (per-seat pricing) and more like 39 cents per request under the new (single pooled cost for everyone). Composer came in a little higher, more like 50c/r, while the claude models were up into the dollars. Meanwhile, if you use Claude-the-app, there is _no_ cheap model and the default switched to Opus in April, resulting in increased costs across the board.
We have both Claude and Cursor here, as well as agents running GPT, things in AWS Bedrock, etc and its my team handle the bills...when people use Cursor on auto, costs are under control, but there's always a dozen or so whale users who'll switch models manually and blow through the budget like it's not there.
Another thing: "better cost controls". There was for example no way for us to disable Fable in Claude, but we could in Cursor. Again, the opposite experience.
Replies
Well, auto can produce garbage code. I'd rather be able to select the model manually myself and so far it's much more economical to give people Claude Code and Codex subscriptions as those are subsidized per seat plans.
For the kind of ML work I do Cursor's "Auto" was too unreliable. It would frequently try to solve relatively difficult tasks using Composer, when it should have been routing to a true frontier model. Annoyingly, doesn't tell you what model it's decided your task deserves, so I often wasted time working through a problem with it, only to realise I was on a dumb model. Then I revert all the work, switch to an expensive frontier model and pay expensive API prices to actually solve the task.
All that is to say, model selection is the main control we have over quality. Giving it up in the name of cost saving will bite you in the long run, especially when Claude Code still has such good plan pricing.