Cursor has become way too slow

I think it’s over. There are too many users who’ve found out abour Cursor in the last few months, and as a result the slow requests have become 10 times slower than it used to be. I’m considering to stop paying for it and move to Aide or run DeepSeek R1 locally as this is not sustainable anymore. It’s killing my productivity with all the waiting time, it’s annoying.

10 Likes

The average waiting time on my end is 3 minutes per request on the Composer lol… You’re right!

are you guys on the paid subscription? my fast requests are still rapid, and even my slow requests are maybe 30 seconds.

With the explosion of AI utilization companies like Cursor have to balance their burn rate from investment, gaining market share, and keeping users happy - very rarely does anyone hit the trifecta.

I’ve played with a bunch of the competitor products and some come close, but none are actively engaged with their user base as much as Cursor.

4 Likes

I am pro - used up all my fast in 2 weeks then used up another 500 fast - now refuse to buy anymore fast. Mostly a balancing lesson to do things myself when there are minor changes. Still… regardless the slow request should not take 3 mins

4 Likes

They have to pay for queries, so you have to pay for queries. Personally it’s worth every single cent, and on the paid plans there is never a wait for queries if you pay for them. Its a fantastic tool, worth 10x what it costs at least.

2 Likes

Personally I agree that cursor with slow requests is unusable.

However, I also consider it worth paying for additional fast requests.

slowsor 3min lol :smiley:

Here my average time is between 15 and 45 seconds on Sonet in the latest version

too slow ,request no reply,i pay for it,why,

Thanku Cursor deepseek r1 is insane sometimes better than claude sonnet