Dear Sir @danperks (and CC: cursor team), I do hope all is well first,
I am consistently learning from experience this week, that when I see a lot of lower quality code, solutions that ignore my prompts and change comments (not code) and create bugs, that I was unaware of being in auto mode.
And that is very frustrating :
1 - there is no transparency of which model I am using, so I never learn from experience which are good and bad for my use cases
2 - I disabled repeatedly auto mode, and was unware when then change to auto happened, this could affect a 3-4h code sprint requiring reverting a git commit and starting again.
I would much rather know there is a capacity problem ( I am aware of them, I know it’s not Cursor fault ) than being diverted to a unknown model, that only proved to be worse , spending, I mean wasting many hours, fast requests listed as Default (ZERO TRANSPARENCY on billing also).
And I am a fan and supporter of cursor, you, @deanrie and this community, but I really feel this non transparent, auto switch is causing a lot of harm, reducing my value and productivity using cursor. I already said in anothe post, seems like a “bad CFO” invented feature to save money, that never coded and will get a fat bonus, not something carefully crafted like most we see here. And I see the posts for ideas using Auto with heuristics and agree it’s the future ideal world.
But let me be clear, I feel disrespected and robbed by this non transparent auto switch and lower quality experience. This is really bad and not in line with all the great work Cursor team has been pushing forward.
Please consider a FAST FIX to disable entirely this maddening and worst update ever for Cursor. If there is anything I can do already, it’s nowehere to be found ( with my skills ). I would greatly appreciate to learn how to get rid of this entirely.
Image references :
-
billing
-
great fix for AI , change the comment to say the same thing and call it a fix :
-
Look at the lousy problem created in Auto mode , confession of a bad decision (context: moved some settings to a central config file, and instead of fixing the methods, names to use it, just add to the code and criticize the solution hardcoding with errors, that I learned and had to fix later :
one comment, for many months I review every change line by line, because the quality for all models varies a lot. Sometimes in a session that you are making simple things in fewer files/context I take some risk with models I trust like Sonnet 3.5 or 3.7 but then the non transparent auto switch caused this , charged as much as premium fast requests, so I rather see a cannot reach anthropic than this, every day , every time .
and you mentioned :
We have previously pushed people to Auto when we’ve struggled for capacity
this is happening this entire week for me.
I hope you read it all. Have a nice friday and weekend !
Cursor information :
( There are currently no updates available.)
Version: 0.47.8
VSCode Version: 1.96.2
Commit: 82ef0f61c01d079d1b7e5ab04d88499d5af500e0
Date: 2025-03-18T06:55:51.040Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0
+
Macbook Pro (m3pro) on Ventura 15.3.2 (24D81)