I’m a heavy user of Cursor (Pro), and Sonnet 3.5 was working reliably until four days ago—handling even slower requests without issue. However, since the launch of Sonnet 3.7, Cursor has become practically unusable. Three days have passed without any response or resolution, so I’ve decided to cancel my Cursor subscription.
1 Like
Hey, can you describe your problem in more detail? Are you getting any errors?
I completely agree! Since Sonnet 3.7 launched, Cursor has become extremely unusable.
Can you believe that It struggles even with enhancing existing frontend code? Something that worked flawlessly before…
It’s so frustrating to see such a downgrade, and the lack of response only makes it worse. It’s like that don’t even know what’s going on or something!
Definitely reconsidering my subscription as well.
1 Like
- I’m in slow requests queue, but Sonnet 3.5 is 10x slower than before 3.7 launch.
- Sonnet 3.7 gets High load every time i’ve tried to use it (I know that’s because of Anthropic Rate Limiting, but this is very frustrating)
Cursor is working with 3.5 for me, but it’s been thick as ■■■■. Honestly, a complete waste of time.
There are so many threads here with people reporting critical issues with even Sonnet 3.5 that is unrelated to slow pool as it occurs even on usage based. Ususally I can use the fast pool for many days but last 3 days literally were so problematic that Cursor is majority of day unusable (and no not because of Anthropic rate limits).
Bug or feature to save token ? claude 3.7 == chatgpt 4o
please see video proof : https://www.youtube.com/watch?v=BhotPfouaS0