Auto had a big improvement a few weeks ago (around when pricing changed)

If a few weeks is months I would agree I think the change to Auto was 2-3+ months ago when they moved to charging named models and higher limits on Auto.

Auto is only good for trivial stuff at this point. It is quite subpar at everything else. Th is is probably because it almost always defaults to Claude Sonnet 3.5 (which you can tell if you ask the agent to identify itself and tell you its version), and that is pretty outdated.

Again it goes back to what your workflow is. I don’t think trivial is the right word. I use auto to write fairly advanced code but I do it in bite size chunks or relatively bite size. So thinking function level or a couple of interdependent functions ruins being written.

I would agree it is not as good on doing lengthy work where it’s taking design all the way through implementing a feature in a single shot but trivial is not a good description.

I also don’t think you’re right. 3.5 was recently deprecated and even before then, Cursor has been hitting rate limits with Anthropic. Auto is as much a token cost optimization as it is a rate limit optimization.